[runtime] Instrument /verify path for chain-test triage#38
Open
[runtime] Instrument /verify path for chain-test triage#38
Conversation
Why: capture CI-visible progress markers around /verify to pinpoint where the failing chain test stalls. Contract impact: none
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.
Motivation
/verifyhandler to determine whether the early cached-only schema guard is being hit and to localize where the failing chain test stalls (ENS resolution, crypto verify, or schema validation).Description
console.errorat/verifythat emitswantSchema,wantEns,verb,VERIFY_SCHEMA_CACHED_ONLY, and the result ofhasValidatorCached(verb).console.error("[verify] entering ENS resolution", { verb })immediately before ENS resolution.console.error("[verify] entering crypto verify", { verb })immediately before callingverifyReceiptEd25519Sha256.console.error("[verify] returning 202 validator_not_warmed_yet", { verb })immediately before the early cached-only202return andconsole.error("[verify] entering schema validation path", { verb, cachedOnly, validatorCached })before fetching/compiling the validator.Testing
node --check server.mjsto validate syntax, which succeeded.Codex Task