Add Graphile build readiness and awaited disposal - #1747
Draft
Zetazzz wants to merge 1 commit into
Draft
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.
Summary
Implements planning item F04 on top of the reusable performance harness in #1716.
createGraphileInstancereturnsBoundary
This PR is intentionally limited to F04 lifecycle foundations in
graphile-cache.It does not add resident-instance admission, heap budgeting, memory-pressure eviction, exact-key build coalescing, a global build coordinator, request draining, realtime-generation lifecycle, new configuration, or server admission behavior. Those remain separate functional units that may consume these primitives later.
No package metadata, lockfile, README, dependency patch, or unrelated package is changed.
Validation
Passed:
graphile-cachelifecycle tests: 3 suites, 13 testsgraphile-cacheCJS and ESM builds@constructive-io/graphql-servertests: 13 suites, 143 testspnpm install --frozen-lockfileunregisterwarning ingraphile-cache.tsremains unchanged)git diff --checkExisting files were audited with zero-context and ignore-whitespace diffs. There is no repo-wide formatting or unrelated formatting hunk; the only indentation changes are inside the rewritten disposal control flow.
Refs constructive-io/constructive-planning#1693.