-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Checking for jid before returning data #55216
Checking for jid before returning data #55216
Conversation
Seems raw can have returns for the same minion, but an other job. In order to not return resutls from the wrong job, we need to check for the jid.
@Ch3LL Could you please take a look here? #52459 (comment) |
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.
not sure what i did wrong previously, but when i patch my local setup i dont see the issue anymore :) thanks for this
ping @brejoc looks like there is a conflict. mind resolving that? if not I can help out |
@Ch3LL Thanks for looking into this again! Seems like the conflicting imports where just removed, so I did the same here. Conflict is solved. Let's see if the tests are still passing for this. |
@dwoz Thanks for taking care of this! 🙇♂️ |
What does this PR do?
Seems raw can have returns for the same minion, but an other job. In order to not return resutls from the wrong job, we need to check for the jid.
What issues does this PR fix or reference?
#50927
This is the successor of #52459.
Previous Behavior
Wrong job results might be returned. Please take a look at #50927
New Behavior
Only the correct jobs results should be returned.
Tests written?
Yes
Commits signed with GPG?
Yes