FuelLabs/sway

forc build invalid channel message cuts the channel

Open

#5,450 opened on Jan 10, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (5,421 forks)batch import
bugforcgood first issue

Repository metrics

Stars
 (61,702 stars)
PR merge metrics
 (Avg merge 5d 4h) (19 merged PRs in 30d)

Description

While testing a PR unrelated to the Sway repo I've been messing around with the manifest file.

On forc version 0.46.0 with the following manifest file

toolchain = { channel = "beta-5" }
components = { forc-wallet = "0.3.0", forc-explore = "0.28.1", forc-run = "0.46.0", forc = "0.46.0", fuel-indexer = "0.21.0", fuel-core = "0.20.5", forc-index = "0.21.0", forc-deploy = "0.46.0", forc-tx = "0.46.0" }

I see the following warning

1

I have changed to beta-5 and it cuts the message to exclude the version number

Contributor guide

Research direction
The issue describes that the error message for an invalid toolchain channel in the manifest file truncates when the channel contains a hyphen (e.g., 'beta 5' shows only 'beta'). To fix, locate the code in the forc tool that validates the channel and formats the error message. Likely in the manifest parsing logic, find where the channel string is printed and ensure the full string is included. Check for any string truncation or formatting issues. Look at the error message construction in the relevant function, possibly in sway lib or the forc source code.
Tech stack
rustshell
Domain
clitooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Basic RustUnderstanding of forc CLI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70