Repository navigation
fix(outbound): narrow recovery blast radius - #782
Merged
Merged
Conversation
Keep pod readiness independent from classified outbound reconciliation while preserving submission gates. Scope recovery blockers to stable end-client references across REST, algos, services, and FIXP ingress, including key-rotation candidates. Closes #780 Closes #781 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
7 tasks
Expect the pod to return to ready after cold-start classification while preserving the missed execution-report replay assertions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
3 of 4 tasks
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.
Summary
/readyroutable after outbound recovery classification completes, while retaining fail-closed order submission for affected scopesTests
dotnet build B3TradingPlatform.slnx --no-restore -c Releasedotnet test backend/tests/B3.Trading.Application.Tests/B3.Trading.Application.Tests.csproj --no-restore -c Release(1990 passed)dotnet test backend/tests/B3.Trading.Api.Tests/B3.Trading.Api.Tests.csproj --no-restore -c Release(688 passed)dotnet test backend/tests/B3.Trading.EntryPointListener.Tests/B3.Trading.EntryPointListener.Tests.csproj --no-restore -c Release(233 passed)dotnet format B3TradingPlatform.slnx --no-restore --verify-no-changesProtocol evidence gate
Does this PR add or change a dependency on B3MatchingPlatform / B3MarketDataPlatform wire behavior?
Checklist:
Closes #780
Closes #781