Repository navigation
Conversation
applied_at defaulted to now(), so releasing holds at fixed instants violated released_at >= applied_at once the clock passed 2026-10-02.
This was referenced Oct 26, 2026
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
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.
What and why
AccountClosurePersistenceIntegrationTesthas failed on every run since 2026-10-02 UTC. Its legal holds tookapplied_at = now()from the database, but the test then released them at fixed instants derived from 2026-08-03. Once the wall clock passed that date, the release violatedreleased_at >= applied_at. Both holds now carry an explicitapplied_aton the test timeline. No production code changes.Replaces #292, which is closed.
Verified
./gradlew testpasses: 1054 tests, 0 failures. The one skip is the opt-in exporter test.Checklist