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.
Implementing `__hash__` and `__eq__` for `BatchedSend`
See original GitHub issueIn Scheduler.report we collect a set of comms for the Clients. Looking more closely at the contents of self.client_comms, it appears to just contain BatchedSend objects. Putting these objects in a set will wind up using __eq__ and __hash__. Neither of these appear to be defined by BatchedSend. As a result a good chunk of time is spent hashing these objects by some fallback mechanism before adding them to the set in Scheduler.report. Would be good to have implementations of __eq__ and __hash__ for BatchedSend to avoid this issue.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Found a good way to do this with a
dict( https://github.com/dask/distributed/pull/4275 ), which should get us past this issue. It may be possible to simplify this further to alist, but that might not matter much.We can also ask @jrbourbeau to do this if y’all are less familiar here. James is fairly adept at these sorts of changes.