Clarify persistence order requirements for async persistence#3951
Merged
joostjager merged 1 commit intolightningdevkit:mainfrom Jul 24, 2025
Merged
Conversation
Specifically, we do not want to imply any persistence order requirements for writes to different keys, but also we don't want to allow state reversions, even if only temporary.
|
I've assigned @joostjager as a reviewer! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3951 +/- ##
==========================================
- Coverage 88.93% 88.93% -0.01%
==========================================
Files 168 168
Lines 121962 121962
Branches 121962 121962
==========================================
- Hits 108471 108466 -5
+ Misses 11088 11087 -1
- Partials 2403 2409 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
👋 The first review has been submitted! Do you think this PR is ready for a second reviewer? If so, click here to assign a second reviewer. |
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
4 participants
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.
Specifically, we do not want to imply any persistence order requirements for writes to different keys, but also we don't want to allow state reversions, even if only temporary.