-
Notifications
You must be signed in to change notification settings - Fork 422
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
keep knowledge of ongoing merges across merge pipelines #5633
base: main
Are you sure you want to change the base?
Conversation
looks like this made |
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.
can you squash the commits and have a good commit message describing your solution?
currently this makes one test very flaky (fails more often than not) and i haven't figured out why yet. i'd rather fix that before merging |
@@ -88,7 +89,7 @@ pub struct DeleteTaskPlanner { | |||
/// a merge operation is dropped after the publish of the split that underwent | |||
/// the delete operation. | |||
/// The inventory is used to avoid sending twice the same delete operation. | |||
ongoing_delete_operations_inventory: Inventory<MergeOperation>, | |||
ongoing_delete_operations_inventory: Inventory<RecordUnacknoledgedDrop<MergeOperation>>, |
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.
typo.
Description
fix #5588
How was this PR tested?
added a test reproducing what was failing before, and making sure it passes now