Add null check for _jobServerQueue #3711
Merged
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.
Added null check for the job server queue in the UpadteMetadata method.
In rare cases, the agent receives a Metadata update message from the server when the job completes and the _jobServerQueue has already been set to null. So the user can see the null refference exception in the pipeline logs:
In the worker logs we can see the following:
This PR should fix this issue
Also added 2 L0 tests:
Test results: