Fix job-match worker notifications#57
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
services.worker_idinstead of non-existentservices.user_id.w["worker_id"]instead ofw["user_id"].job_matchnotification for a matching active service worker.Root cause
The job creation path queried and read the wrong worker column, then swallowed the exception in the notification best-effort block. Jobs could be created successfully while matching workers were never notified.
Test Plan
python3 -m unittest test_deep_audit_regressions.BackendRegressionTests.test_job_creation_notifies_matching_service_workerspython3 -m unittest test_deep_audit_regressions.pypython3 -m unittest test_diagnostics.py