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
Faulty assert in Worker.transition_waiting_ready #2763
Comments
Ah, interesting point. We could either ignore that or do a more expensive check. I don't have a strong preference. |
@TomAugspurger , did you mean to fix this? |
Nope. Not a priority for me.
Fixing it would I think require an O(N) step to extract the key from the
priorities `set(x[0] for x in self.priority)`. Not sure if that's too
expensive when `validate=True`.
…On Wed, Jun 19, 2019 at 1:10 PM Martin Durant ***@***.***> wrote:
@TomAugspurger <https://github.com/TomAugspurger> , did you mean to fix
this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2763?email_source=notifications&email_token=AAKAOIVHSZLR723UYTEH6YDP3JZDDA5CNFSM4HWWLJE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYCWPKQ#issuecomment-503670698>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIUFAIAXJXDXIEFV3LTP3JZDDANCNFSM4HWWLJEQ>
.
|
So it would be more correct to say that the validate=True branch is not tested or called anywhere? |
I imagine it's tested. It's just that the `assert` is vacuously true since
we're doing something like `assert 'a' not in [('b', 0), ('c', 1)]`, when
we want `assert 'a' not in ['b', 'c']`.
…On Wed, Jun 19, 2019 at 1:16 PM Martin Durant ***@***.***> wrote:
So it would be more correct to say that the validate=True branch is not
tested or called anywhere?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2763?email_source=notifications&email_token=AAKAOIWBX3AFYIOC3PX4OY3P3JZYNA5CNFSM4HWWLJE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYCW7QA#issuecomment-503672768>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIT6LZ4D6J3XAGK3F2DP3JZYNANCNFSM4HWWLJEQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think the assertion in
distributed/distributed/worker.py
Line 1464 in d378b41
self.ready
will have priorities. Adding some loggingouptuts
The text was updated successfully, but these errors were encountered: