-
Notifications
You must be signed in to change notification settings - Fork 803
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
Fix user queue in scheduler that was not thread-safe #6077
Fix user queue in scheduler that was not thread-safe #6077
Conversation
Signed-off-by: Justin Jung <jungjust@amazon.com>
a4a9f6d
to
d505f87
Compare
9eaf463
to
50ea14a
Compare
50ea14a
to
b7dd40a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks Justin.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, yes, there is a data race there. And I believe your proposed fix and test for the race are appropriate. I have only nits on covering all the changes with the test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks
Signed-off-by: Daniel Blando <daniel@blando.com.br>
What this PR does:
Which issue(s) this PR fixes:
Fixes an issue where user queue in scheduler wasn't thread-safe
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]