You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's doesn't appear to be any handling of special shell characters in gift when options and arguments are passed to bash.
A path with spaces or special characters in the arguments will blow up with
Unhandled rejection Error: spawn /bin/sh ENOENT
at exports._errnoException (util.js:874:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at doNTCallback2 (node.js:439:9)
at process._tickCallback (node.js:353:17)
Unhandled rejection Error: ENOENT: no such file or directory, open '/app/fixture/re po/event_rules_spec.yml.saved'
at Error (native)
Trying to escape paths at the front end causes more issues so I think it needs to be handled in gift.
There's doesn't appear to be any handling of special shell characters in gift when options and arguments are passed to bash.
A path with spaces or special characters in the arguments will blow up with
Trying to escape paths at the front end causes more issues so I think it needs to be handled in gift.
The Shellwords module from ruby has the most useful shellescape implementation I've used.
The best nodejs example I could find is on stack:
Do all exec calls in gift go through the
git
function? Is it normallyargs
that would pass path/file names?The text was updated successfully, but these errors were encountered: