Toolchain installation fails with "GitHub API returned status code: 401 Unauthorized"
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing the GitHub API request used by espup install to fetch the latest Xtensa Rust version; the issue provides the failing command and 401 response but names no source file or test. Reproduce with espup 0.17.1 and inspect the API call and its error handling. Done when installation handles the reported 401 as intended and a test covers that response.
Written by the indexing model from the issue text.
Description
Bug description
I'm following the instructions for installing via espup on https://docs.espressif.com/projects/rust/book/getting-started/toolchain.html#xtensa-devices and I'm unable to install anything. The instructions don't list any alternatives.
To Reproduce
Steps to reproduce the behavior:
- Install espup with
cargo install espup --locked - Run
espup install
Expected behavior
espup should be installed, as the docs say.
Screenshots
$ cargo install espup --locked
Updating crates.io index
Downloaded espup v0.17.1
Downloaded 1 crate (58.5KiB) in 0.07s
Installing espup v0.17.1
[...]
Compiling update-informer v1.3.0
Compiling espup v0.17.1
Finished [`release` profile [optimized]](https://doc.rust-lang.org/cargo/reference/profiles.html#default-profiles) target(s) in 43.56s
Installing /Users/seancross/.cargo/bin/espup
Installed package `espup v0.17.1` (executable `espup`)
$ espup install
[warn]: A new version of espup ('v0.18.0') is available
[info]: Installing the Espressif Rust ecosystem
[warn]: Failed to get latest Xtensa Rust version: HTTP GET Error: GitHub API returned status code: 401 Unauthorized
Error: espup::toolchain::http_error
× HTTP GET Error: GitHub API returned status code: 401 Unauthorized
$
Environment
- OS: macOs 26.5.2 (25F84)
- espup version: 0.17.1
Additional context
The command says v0.18.0 is available, but cargo install doesn't seem to know about it.
- Dominant language
- Rust
- Stars
- 464
- Forks
- 37
- Avg merge
- 17h 29m
- Merged PRs (30d)
- 7
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 esp-rs/espup
-
espup reports 0.18.0 is available, even though it's notPossibly taken @SergioGasquez claimed this 4 days ago. Openbug bug jury
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
enhancement feature request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Install To Platform-Standard Locations | Reduce Home Directory ClutterMay be free again A pull request for this issue was closed without being merged. Openenhancement feature request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement feature request
Difficulty 3/5 1-2 days Newbie friendliness 42/100
Similar issues
-
documentation enhancement SIEM
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ADORSYS-GIS/wazuh-agent-status#265 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
manuscript-lang/manuscript#1629 ·
Maintainers usually reply within 1 day
-
autofixer: follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
tursodatabase/turso#10885 ·
Maintainers usually reply within 1 day
-
🐞 bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nannou-org/gantz#475 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100