Release artifacts can't easily be used in macOS?
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
While working on https://github.com/cloudamqp/homebrew-cloudamqp/pull/33 I ran into
The binary exits with code 1 during install — likely a macOS codesigning/quarantine issue with the pre-built binary being executed during the install phase.
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.
Research direction
Start by reproducing the macOS installation described in homebrew-cloudamqp/pull/33 and inspect the pre-built binary's codesigning or quarantine behavior during install. Done means the release artifact installs and runs successfully on macOS without exiting with code 1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100