New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging an object with incompatible type kills Dask worker #7471
Comments
Also make the function conform to its specified type signature. :-)
Thanks for reporting this @uellue ! It is a bug that the worker/server is dying. This should clearly not happen. However, that the msg has to be msgpack serializable is document, at least in the the Client.log_event. In #7472 I added doc strings to the respective Worker/Nanny methods and implemented a check that raises a hopefully better error message w/out killing the worker. |
Thx for the quick reply and for taking care of it! |
Also make the function conform to its specified type signature. :-)
Also make the function conform to its specified type signature. :-)
Logging an event with an object type that is not handled by
msgpack
kills a Dask worker. I am not sure iflog_event()
should work with such types or if it is the user's responsibility to only use compatible types?Resulting error message on the terminal:
Anything else we need to know?:
Not sure if this is a bug or if the allowed types in log messages should be specified!
Environment:
The text was updated successfully, but these errors were encountered: