This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
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.
Process previously failed backfill events in the background #15585
Process previously failed backfill events in the background #15585
Changes from all commits
fd26164
c5dc746
8fc47d8
b5d95f7
ebc93be
e13f5a9
70f5911
45934fe
b1998d7
93de856
631d7db
beeccc3
7eabc60
7583c2c
e101318
899fc34
b5aec4f
6edd126
d4b8ff7
6a0ec9d
d843557
75bec52
c4e1533
ec230a3
22a69be
65febed
6474b4e
15527f7
d59615f
95ffa7c
50acf6a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Continuing from previous comment,
The test passes even without this
pump()
. I'm uncertain about the exact intricacies and details ofrun_as_background_process(...)
that allow it to pass. It is possible that the test passes due to its time-sensitive nature, and without thepump()
, it might become flakey. However, these are merely theoretical assumptions.But I want to ensure that this test is robust to any work that may happen in
run_as_background_process(...)
in the future. Ideally, we would have an idiomaticwait_for_background_processes()
that would indicate clear intentions and handle the complexity of whatever waiting is necessary.