⬆️ deps: bittensor 10.5 + btcli 9.23 for multi-mechanism chain runtime - #194
Merged
Conversation
bittensor 10.1.0 can no longer query the live chain: the multi-mechanism runtime migration wrapped netuid storage keys in a NetUid newtype, so Subtensor.metagraph(netuid) dies with "Invalid type for data: 102 of type <class 'int'>" on both finney and archive. Validator bootstrap calls metagraph() (run._sync_lite_metagraph), so any :stable container restart crash-loops fleet-wide. Bump to bittensor 10.5.0 / bittensor-cli 9.23.2 and move the async-substrate-interface pin to the cyscale-based 2.2.1 (both new pins require it; the old scalecodec-era 1.6.4 hack is obsolete — btcli no longer pulls py-scale-codec). Verified in a clean python:3.10 container and layered over the :stable image on a live host (137.184.170.154): deps resolve with no scalecodec, all connito validator/shared modules import, metagraph returns n=256 on netuid 102, and the validator bootstraps through chain-commit fetch and model load. bittensor 11.0.0 was rejected: it removes Subtensor.metagraph and needs a real migration. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…r 0.26) CI's clean-image build caught two conflicts the layered container test could not: bittensor 10.5.0 requires requests>=2.33 (repo pinned 2.32.3) and bittensor-cli 9.23.2 requires typer~=0.26 (repo pinned 0.24.1). Verified with a full pip dry-run resolve of requirements.txt in a clean python:3.10 container against the cu124 index. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
bittensor 10.1.0 can no longer query the live chain: the multi-mechanism runtime migration wrapped netuid storage keys in a NetUid newtype, so Subtensor.metagraph(netuid) dies with "Invalid type for data: 102 of type <class 'int'>" on both finney and archive. Validator bootstrap calls metagraph() (run._sync_lite_metagraph), so any :stable container restart crash-loops fleet-wide.
Bump to bittensor 10.5.0 / bittensor-cli 9.23.2 and move the async-substrate-interface pin to the cyscale-based 2.2.1 (both new pins require it; the old scalecodec-era 1.6.4 hack is obsolete — btcli no longer pulls py-scale-codec).
Verified in a clean python:3.10 container and layered over the :stable image on a live host: deps resolve with no scalecodec, all connito validator/shared modules import, metagraph returns n=256 on netuid 102, and the validator bootstraps through chain-commit fetch and model load. bittensor 11.0.0 was rejected: it removes Subtensor.metagraph and needs a real migration.