Repository navigation
Preserve public publication waits during incomplete recovery - #208
Merged
Merged
Conversation
Collaborator
Author
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
p0mvn
force-pushed
the
codex/remove-initial-query-delay
branch
from
October 15, 2026 22:31
78a1a4d to
d969b13
Compare
p0mvn
force-pushed
the
codex/public-recovery-service-wait
branch
from
October 15, 2026 22:35
1c7c85f to
4cad4c2
Compare
p0mvn
marked this pull request as ready for review
October 15, 2026 22:48
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
1 participant
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.
Summary
When a transparent publication ends below the wallet's target, a failed private entry could hide that public lag and remove the service retry delay. Preserve the public lag result independently of private content failures, while retaining the longer overload wait, actual coverage, and the existing failed-entry hold policy.
This is stacked on #205, the revision Vizor already uses, so the repair does not pull unrelated release changes into its dependency update.
Breaking changes
Validation
A regression through the real PIR service and adapter reproduced the missing delay before the repair. It compares healthy and malformed selected entries under the same lagging publication. Boundary coverage checks every progress outcome and preserves the longer overload delay. The complete adapter configuration passed, including recovery through the in-process PIR service, detail and discovery recovery, and documentation examples. No live service or app deployment is involved.