Improve output for unsupported one-part channel in dotnet-install.sh
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- bash
- Domain
- cli
Research direction
Start in dotnet-install.sh by tracing channel validation and the path reached by bash dotnet-install.sh -c 10 --verbose. Compare the existing help text with the resulting error and verify the unsupported one-part channel no longer triggers a 404 attempt. Done means the output explains the supported formats and suggests using a two-part channel such as 10.0.
Written by the indexing model from the issue text.
Description
When a one-part channel (e.g. -c 10) is specified for dotnet-install.sh, the script attempts to resolve it and fails with unclear messaging. The output currently attempts to download files for the one-part channel, leading to a confusing 404 error. The script help text specifies that channels must be 'STS', 'LTS', a two-part version (A.B), or a three-part SDK band (A.B.Cxx), but this expectation isn't reflected in the error message.
Request:
- Detect if a one-part channel is given and update the output to indicate it is not valid.
- Make the error message clear about supported channel formats and provide a suggested workaround (e.g. use
-c 10.0).
This will help users avoid confusion and parallels a similar situation described in issue #685 (and previously #461).
Repro:
bash dotnet-install.sh -c 10 --verbose
# output is unclear, attempted downloads fail with 404
Expected:
- Clear error about channel format and workaround.
- Dominant language
- PowerShell
- Stars
- 213
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/install-scripts
-
area-infra
dotnet/install-scripts#699 · 2 reactions · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
dotnet/install-scripts#595 · 5 comments ·
-
needs-pm-discussion
Difficulty 5/5 Over a week Newbie friendliness 35/100
dotnet/install-scripts#583 · 1 comment · 2 reactions ·
-
needs-pm-discussion
Difficulty 5/5 Over a week Newbie friendliness 35/100
dotnet/install-scripts#580 · 1 comment · 5 reactions ·
-
needs-pm-discussion
Difficulty 3/5 1-2 days Newbie friendliness 42/100
dotnet/install-scripts#578 · 4 comments · 1 reaction ·
All issues in dotnet/install-scripts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
alexgorbatchev/dotfiles#107 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
from:qa priority:P2 reliability tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spec-kitty/spec-kitty#4874 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·