-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Path escaping for rebar shell command in deps.compile.ex #13750
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
Comments
@gdyr can you please send a PR with your changes so far? I don't see why a space on the path to rebar would be a problem. |
Actually, the root problem is here: https://github.com/elixir-lang/elixir/blob/main/lib/mix/lib/mix/rebar.ex#L218 |
josevalim
pushed a commit
that referenced
this issue
Jul 31, 2024
Closing in favor of the PR: #13751 Thanks! |
josevalim
added a commit
that referenced
this issue
Jul 31, 2024
…13751) Closes #13750. Co-authored-by: Michael Goodyear <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
elixir/lib/mix/lib/mix/tasks/deps.compile.ex
Line 210 in 99be673
Compilation of Phoenix dependency "telemetry" using Rebar fails when parentheses (or presumably other shell-significant characters) appear in the project path.
This is due to inadequate escaping in
escape_path()
...elixir/lib/mix/lib/mix/tasks/deps.compile.ex
Line 225 in 99be673
... but could be avoided by using
System.cmd()/3
instead ofMix.shell().cmd()
, to pass arguments without needing to escape them.I've attempted a fix in 806a889, but this breaks the case where there is a space in the path to
rebar
- if I get more time, I'll continue investigating, but perhaps someone else may want to pick this up in the meantime?The text was updated successfully, but these errors were encountered: