Fix edge case where KO_DATA_PATH is defined but no valid config is found#135
Merged
Conversation
When the ordered lookup exhausts both candidates without finding a readable file, the error now names every path tried. The ko-data-path candidate is also stat'd before being returned, so a local operator with KO_DATA_PATH inherited from a parent shell sees a meaningful fallback to ./pkgproxy.yaml rather than a confusing single-path error. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…date Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
45f5763 to
b0ff5fd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.