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
DM-36172: Add explicit transaction around moveToTrash calls #733
Conversation
Modern mypy does not want it.
Codecov ReportBase: 84.69% // Head: 84.68% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #733 +/- ##
==========================================
- Coverage 84.69% 84.68% -0.02%
==========================================
Files 244 244
Lines 32141 32156 +15
Branches 6034 6040 +6
==========================================
+ Hits 27222 27230 +8
- Misses 3745 3752 +7
Partials 1174 1174
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
I've requested some adjustments that I do think need to be made, but I think they're straightforward (and I'm about to disappear), so I'm happy to let you take it from here.
Butler does not know that a registry transaction is sufficient. This also add a transaction parameter to bridge moveToTrash method to make use of that new transaction context. Without this there is no way for the ephemeral bridge to roll back a transaction from a failure in registry. This works for the normal bridge because that is also using a shared database transaction.
4139289
to
a782053
Compare
Without this the in-memory datastore can not rollback a
datastore.trash()
call.Checklist
doc/changes