Refactor JobRepository to remove wait timeouts. - #94
Merged
Conversation
…mmit by commit to closely monitor test changes.
adeutscher
marked this pull request as ready for review
August 23, 2026 01:05
Owner
Author
|
Before I commit this, confirming that it was intentional to leave |
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.
This change deals with a long-standing code-smell in JobRepository. Two public methods,
GetNextJobAsyncandWaitForEmptyRepositoryAsync, involved wait calls on events with a 250ms timeout to re-poll the source of truth. While it was functional and didn't have a high performance cost, the implementation never sat well with me.