bot: fix race-condition in dispatch #1728
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Exirel
added
Medium Priority
Bugfix
dgw
requested changes
Oct 27, 2019
Exirel
force-pushed
the
fix-race-condition-on-reload
branch
from
082ba78 to
608f673
Compare
|
Fixed!
Yup, and I believe an overhaul of |
dgw
approved these changes
Oct 30, 2019
Exirel
force-pushed
the
fix-race-condition-on-reload
branch
from
6b8d4ba to
2ec778f
Compare
|
All squashed into one single commit! |
|
@Exirel This is approaching the top of the merge queue, but it has a conflict now. :/ |
The scenario is: * dispatch is called for a pretrigger * it looks into the list of callable by priority * it triggers one of the first callables, which wants to remove a callable of the same priority * because Python must not allow a dict to be modified while it is iterated over, Python raises an exception If we put a lock here, Python won't raise the exception... but we'll get a deadlock. To prevent that, instead, we copy the list of callables, and return the ones that are triggered. If any of them wants to change the callables of the same priority, they won't raise an error, because we are not iterating anymore on the dict. Hoo-ray! (with applied review suggestions from dgw) Co-Authored-By: dgw <dgw@technobabbl.es>
Exirel
force-pushed
the
fix-race-condition-on-reload
branch
from
2ec778f to
59704e6
Compare
|
Conflict fixed. That was just the little |
dgw
added a commit
that referenced
this pull request
Nov 22, 2019
Assigning the tuple returned by `_is_pretrigger_blocked()` to both vars instead of unpacking the values makes both of them always evaluate to `True` in Boolean contexts. Which magically blocks everyone from doing anything, unless `get_triggered_callables()` decides they're unblockable by virtue of `trigger.admin` being `True` (or if the function is marked unblockable, of course). Fun times! Introduced by #1728 — `.blame Exirel`! I share no responsibility for missing this in code review. Nope, none at all. :P Let this be a lesson to us all: Test things as a non-admin sometimes. Just in case. (New testing infrastructure should help us catch this sort of thing automatically in a lot of cases, once our unit tests have been updated to use the new mocks.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The scenario is:
If we put a lock here, Python won't raise the exception... but we'll get a deadlock. To prevent that, instead, we copy the list of callables, and return the ones that are triggered. If any of them wants to change the callables of the same priority, they won't raise an error, because we are not iterating anymore on the dict.
Hoo-ray!
@dgw have fun with my miserable grammar at 2am.