Repository navigation
Bound Fabric readiness checks without full table scans - #180
Merged
Merged
Conversation
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.
Fabric readiness currently scans every RAW and audit row on each status request. As those tables grow, the scan can exceed the status deadline and make an available catalog appear unavailable. Probe the database and required relations with a bounded read-only query instead, and report unmeasured counts as unknown.
When a queued-proposal threshold is configured, an unknown count now degrades the health check instead of being treated as zero. The REST and MCP response fields remain present.
Validation: full suite (1,214 passed, 9 skipped), 83 focused tests, independent review. PostgreSQL permission and timeout behavior still requires an isolated real-server integration check.