Consider enabling cgo or creating a work around for functions that require it
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Per https://github.com/mozilla/sops/pull/353 - the use of os/user's user.Current() requires cgo. We are currently using that functions in a few places, and all of our releases (except the Docker container) have cgo disabled.
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 reviewing pull request #353 and tracing the places that call os/user's user.Current(). Compare the cgo-disabled release builds with the Docker build, then determine whether enabling cgo or a workaround is appropriate. Done means the affected functions work in the non-Docker releases without introducing a new release-build failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100