fix(deploy): actionable error when cargo metadata fails (#396)#461
Open
illegalcall wants to merge 1 commit into
Open
fix(deploy): actionable error when cargo metadata fails (#396)#461illegalcall wants to merge 1 commit into
illegalcall wants to merge 1 commit into
Conversation
Contributor
|
Dev build ready — try this branch: |
Contributor
E2E Test Pass · ❌ FAILTag:
❌ Failed tests (1)
Sentry traces: view spans for this run |
Remap cdm-builder's raw "Command failed: cargo metadata ..." dump to a message that explains the likely causes and keeps cargo's own file/line, so a bad Cargo.toml stays fixable.
illegalcall
force-pushed
the
fix/396-cargo-metadata-actionable-error
branch
from
July 21, 2026 05:49
6e45105 to
2ce7c9b
Compare
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
2 participants
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.
What
cargo metadatafailures during contract deploy dumped cdm-builder's rawCommand failed: cargo metadata ... --no-deps. Remap it to an actionable message, mirroring the existing IPFS-migration remap.Achieved
Clear guidance (Rust toolchain / network / bad Cargo.toml) plus cargo's own file and line, instead of a bare command echo.
Works
error: key with no value --> Cargo.toml:21:6.Doesn't
cargo metadatafails in the first place (environmental: cold git-dep fetch, missing toolchain, or bad manifest). This covers the actionable-error half of [BUG] pg mod: contract deploy fails — "cargo metadata --format-version 1 … --no-deps" #396, so leaving the issue open for the rest.