If the source sync of a private package manifest repo fails, installation falls back to the public repo
Open
bug
- Dominant language
- Go
- Stars
- 926
- Forks
- 111
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Description
This is even if the previously synced private repo contains manifests overwriting the ones in the public repo
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named in the issue. Start by reproducing installation after a failed private manifest repository sync, then trace the source-selection behavior. Done means previously synced private manifests continue to take precedence over manifests from the public repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100