msitarzewski / msitarzewski/brew-browser
[brew-browser] Upgrade-all failed
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 30
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 6
Description
brew-browser: 0.6.0
Homebrew: 6.0.20
Error code: brew_exit_non_zero
Command: brew upgrade
Exit code: 1
stderr excerpt:
==> Downloading Homebrew API data
✔︎ JSON API packages.sequoia.jws.json
Error: node: no bottle available!
If you're feeling brave, you can try to install from source with:
brew install --build-from-source node
This is a Tier 3 configuration:
https://docs.brew.sh/Support-Tiers#tier-3
Do not report any issues to Homebrew/* repositories!
Read the above document instead before opening any issues or PRs.
==> Fetching downloads for: simdjson
Error: node: no bottle available!
If you're feeling brave, you can try to install from source with:
brew install --build-from-source node
This is a Tier 3 configuration:
https://docs.brew.sh/Support-Tiers#tier-3
Do not report any issues to Homebrew/* repositories!
Read the above document instead before opening any issues or PRs.
✔︎ API Source simdjson.rb
✔︎ API Source node.rb
✔︎ Bottle Manifest cmake (4.4.3)
✔︎ Formula simdjson (4.6.9)
✔︎ Bottle cmake (4.4.3)
Replace this line with what you were doing when the error appeared, and what you expected to happen.
Contributor 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.
Research direction
Start by reproducing the brew upgrade failure from brew-browser's upgrade-all action and compare it with the captured stderr. Trace how brew_exit_non_zero is surfaced; done means the expected behavior is clarified and the relevant regression coverage verifies it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100