-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fetch: Fix various issues related to zig fetch --save
#21931
Open
castholm
wants to merge
5
commits into
ziglang:master
Choose a base branch
from
castholm:fetch-path
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+89
−33
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7867b74
fetch: Disallow `--save` when fetching by file path
castholm e353694
fetch: `--save` over existing `path` entry correctly
castholm 2ee8bda
fetch: Fix fetching by file URL
castholm 33d2a58
fetch: Remove some redundancy from usage text
castholm 9da3e10
fetch: Update tests
castholm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just want to note that this does mean that if the user invokes a command like
zig fetch --save ./foo.tar.gz
, the package will first be copied to the global cache before printing the error. This is obviously not perfect; ideally, the command should detect that the user passed a file path in combination with--save
and exit before doing any work. However, if we want a maximally consistent and correct behavior, each solution comes with its own downsidespath_or_url
input is a directory we can open, then a file we can open, then finally a URL. Moving this logic to thecmdFetch()
function before we actually fetch the package would mean we now have open file handles that we need to pass to therun()
function and correctly close them if any errors occur on the way there (but not ifrun()
returns an error sincerun()
claims ownership of the handle). This is not trivial and will result in ugly code.c:foo
(on Windows) orhttp:foo
(on POSIX) would be interpreted as a URL despite possibly being a valid file path, so this isn't ideal. Even if we try to rule out values we know are not valid URLs that can be fetched, an input likehttp://example.com/example.tar.gz
could be a valid file path to the subpathexample.com/example.tar.gz
inside the directoryhttp:
.zig fetch --path http:foo --save
.I've thought about this a lot and I'm sure what the best way to handle this is, or if it's even worth putting energy into. I just think edge cases matter, however obscure they might be.