Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sample config file isn't in a working format

See original GitHub issue

With distributed 1.25.1, if you start up with no configuration file, one is created for you in: ~/.config/dask/distributed.yaml

This starts:

# distributed:
#   version: 2
#   # logging:
#   #   distributed: info
#   #   distributed.client: warning
#   #   bokeh: critical

If you were to remove the hashes and try to use the config file as is, it doesn’t work – the code still expects the old-style config files., for example, dask.security does not look under the key distributed.comm. for tls, it expects it at the top level.

Issue Analytics

State:
Created 5 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

jrbourbeaucommented, Apr 22, 2020

I don’t think so. However, this issue may have already been fixed by https://github.com/dask/distributed/pull/2873. cc @jcrist

@prasunanand as a side note, all conversation around Dask development takes place on GitHub so if there’s not a comment indicating that someone is working on an issue, then feel free to jump in

1reaction

mrocklincommented, Dec 17, 2018

In particular if you search distributed/security.py for dask.config.config you’ll find that this dictionary is passed into some function that hopefully grabs the relevant information from it. My guess is that we instead need to pass in dask.config.get('distributed.comm.tls') or something similar (maybe dask.config.get('distributed.comm') or something else).

I don’t personally have a good way to test this, but @rbubley might have suggestions.