You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike Future.addCallback, Future.callback= clears the callback list which prevents previously registered listeners from being notified. This can cause hard to debug hangs. I ran into this when using all() to wait for all input edges in a graph, some of which were also transitive dependencies. I think Future.callback= should be deprecated and possibly removed in favor of addCallback. If there are cases where the existing behavior is needed, clearCallbacks should be made public so that it can be done explicitly.
I'm about to file a PR to fix all(). I tried doing a wider sweep of callback= but that caused some tests to fail and I didn't have time or experience to really dig into them.
The text was updated successfully, but these errors were encountered:
Unlike Future.addCallback, Future.callback= clears the callback list which prevents previously registered listeners from being notified. This can cause hard to debug hangs. I ran into this when using all() to wait for all input edges in a graph, some of which were also transitive dependencies. I think Future.callback= should be deprecated and possibly removed in favor of addCallback. If there are cases where the existing behavior is needed, clearCallbacks should be made public so that it can be done explicitly.
I'm about to file a PR to fix all(). I tried doing a wider sweep of callback= but that caused some tests to fail and I didn't have time or experience to really dig into them.
The text was updated successfully, but these errors were encountered: