Repository navigation
Isolate Article Work topology declaration failures - #239
Merged
enteriaza merged 1 commit intoOct 21, 2026
Merged
Conversation
enteriaza
deleted the
194-bug-isolate-article-work-topology-declaration-failures
branch
October 21, 2026 18:52
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
Fixes #194 by isolating Article Work topology declaration failures so that one incompatible backbone queue cannot prevent other backbones from becoming available.
Previously,
EnsureProviderTopologyAsyncdeclared all missing backbones using a single manual-ack channel. If a quorum queue declaration failed withPRECONDITION_FAILED, RabbitMQ closed the channel. Subsequent declarations continued on the unusable channel, preventing later backbones from being declared on each reconciliation pass.Changes
Channel failure isolation
Improved diagnostics
PRECONDITION_FAILEDincompatibility visible rather than reporting only cascading channel-closed failures.Regression tests
406 PRECONDITION_FAILEDdiagnostics.No queues are deleted, purged, or recreated automatically. Existing incompatible queues still require an operator to resolve the underlying topology mismatch.
Validation
dotnet format VectorNNTPD.slnx --verify-no-changes: passedOutcome
A failed topology declaration for one backbone no longer blocks subsequent independent backbones. The existing reconciliation mechanism can retry failures while already-running consumers remain undisturbed.