-
Notifications
You must be signed in to change notification settings - Fork 372
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
Tokenize OPAMFETCH value properly, not splitting by whitespaces #5490
Labels
Comments
Thanks for opening this bug report. I don't think opam has the necessary code to parse commands so I've sent a message to @dbuenzli to see how we can leverage his code without pulling all the dependencies from |
It works! Thanks for the fix 👍
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because OPAM splits OPAMFETCH value by spaces, the use-case below does not work as expected.
As you may see in the log,
"Authorization: token ..."
argument is parsed into seperate words.OPAM should tokenize OPAMFETCH value in the way shell tokenizes[1, 2], so that a quoted argument is parsed as a single string rather than separate words.
[1] https://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html
[2] https://github.com/dbuenzli/bos/blob/master/src/bos_cmd.ml#L46-L112
The text was updated successfully, but these errors were encountered: