Fix to lazily configure the warg client#110
Merged
calvinrp merged 1 commit intobytecodealliance:mainfrom May 13, 2024
Merged
Conversation
|
I can confirm it fixes the problem I ran into. Thank you! |
Collaborator
|
Probably worth investigating if other wac commands could use a similar change |
macovedj
approved these changes
May 13, 2024
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
3 participants
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.
Fix for #109
Calling
FileSystemClient::new_with_default_config()was triggering a call to get theauth_tokenfor the globally configured Warg registry: https://github.com/bytecodealliance/registry/blob/main/crates/client/src/lib.rs#L1404If only local file paths are used, this is not needed and shouldn't happen.