Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
luismeyer
added this pull request to stack #512
September 23, 2026 13:34
luismeyer
force-pushed
the
codex/flags-client-debug
branch
from
September 30, 2026 14:56
09a8e94 to
f50ca9f
Compare
luismeyer
force-pushed
the
codex/flags-client-debug
branch
from
October 1, 2026 10:30
f50ca9f to
0768d43
Compare
luismeyer
force-pushed
the
codex/flags-client-debug
branch
from
October 1, 2026 10:54
2dac318 to
76e3975
Compare
luismeyer
force-pushed
the
codex/flags-client-debug
branch
from
October 1, 2026 11:00
76e3975 to
7abefe2
Compare
luismeyer
force-pushed
the
codex/flags-client-debug
branch
from
October 1, 2026 11:49
7abefe2 to
4925dc8
Compare
This branch was successfully deployed
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.
Stacked on #511 (
codex/flags-header-source), including its unified project-aware reads and immediate stream fallback fixes.Set
DEBUG=@vercel/flags-coreto follow the controller, shared cache, and network sources through one globalconsole.debuglogger. Every event includes the configuredclientName, so concurrent clients can be distinguished.State transitions include their previous state, next state, and reason. Evaluation and
getDatafile()events show the project, revision, age, freshness assessment, and failure allowance. Refresh events distinguish background, blocking, and shared work; HTTP response receipt is separate from cache application. Stream-confirmed cancellation is distinguished from shutdown, and ordinary freshness confirmations do not look like outage recovery. Polling/stream startup logs expose timeout and freshness thresholds; HTTP retries and stream reconnects include attempt counts, delays, and reasons.getDatafile()logs use its API name because it now performs active resolution.Logging remains off by default, checks the namespace on each call, and computes details lazily. Diagnostics omit credentials, raw headers, definitions, evaluation entities, and raw error messages; a throwing console cannot interrupt client operations. The README includes an example trace and an event guide. Event names and fields are internal diagnostics.
Validation after rebasing: 995 core unit tests across 23 suites pass on both Node 22 and Node 24. TypeScript, the core build, changed-file Biome, and
git diff --checkpass. A built-package smoke check verifies client names across four concurrent clients, header refreshes, polling, quiet stream timeout/reconnect, and shutdown. The adapter discovery fixture now covers lazy stream initialization; its 13 tests pass on Node 22 and Node 24 (one existing test remains skipped). All 26 definition-preparation tests also pass. Live-service integration tests were excluded.