Fix bad start call error name#2811
Conversation
🛡️ AI Review — Skeptic (security review)VERDICT: SAFE BASELINE scrutiny: established write-permission opentensor contributor; no Gittensor allowlist hit found; branch fix-start-call-error -> devnet-ready. No FindingsNo findings. Prior-comment reconciliation
ConclusionThis PR is a narrow runtime error rename plus the required runtime 📜 Previous run (superseded)
🔍 AI Review — Auditor (domain review)VERDICT: 👍 Gittensor association: UNKNOWN (no allowlist hit); author is an established write-permission opentensor contributor. PR body was empty/trivial; the Auditor has auto-filled it. Please review. No domain findings. The PR appends the corrected I did not run build/tests; static review was sufficient for this narrow runtime error rename. FindingsNo findings. ConclusionThis is a minimal runtime metadata/error-name fix with the spec bump included. I found no correctness, safety, migration, weight, origin, or duplicate-work issue that should block merge. |
|
🔄 AI review updated — Skeptic: VULNERABLE |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
Description
Fixes the misspelled start-call readiness error returned by
do_start_call.What Changed
StartCallNotReadypallet error.pallets/subtensor/src/subnets/subnet.rssodo_start_callreturnsStartCallNotReadywhen the subnet has not waited enough blocks after registration.runtime/src/lib.rsspec_versionfrom 423 to 424 because the runtime metadata/error surface changes.Behavioral Impact
The start-call readiness check is unchanged. Calls made before
StartCallDelayhas elapsed still fail, but now report the correctedStartCallNotReadyerror instead ofNeedWaitingMoreBlocksToStarCall.Testing
Not specified in the PR body. This is a narrow error rename with no logic change.