unable to run application, when invoked from a path with & in a folder name

[Igor-Pchelko]

Pre issue-raising checklist

I have already:

• Upgraded to the latest version of the relevant libraries
• Checked to see if the issue has already been raised

Software versions

• https://github.com/pact-foundation/pact-ruby-standalone/releases/tag/v1.85.0
• Mac OSX 10.15.5

Expected behaviour

curl -LO https://github.com/pact-foundation/pact-ruby-standalone/releases/download/v1.85.0/pact-1.85.0-osx.tar.gz
tar xzf pact-1.85.0-osx.tar.gz
cd pact/bin
./pact-mock-service --help start

./pact-mock-service --help start Should return help information.

Actual behaviour

./pact-mock-service --help start returns error.

./pact-mock-service --help start

/Users/__removed__/_R&D/pact/pact/lib/ruby/bin/ruby: line 14: D/pact/pact/lib/ruby/lib/ruby/gems/2.2.0: No such file or directory

[Igor-Pchelko]

Looks like the issue is similar to the: #37

But in my case the base directory was __R&D.
And self contained pact can't resolve the path on OSX with symbol &.

[Igor-Pchelko]

May be it's related to the issue with path on OSX: phusion/traveling-ruby#94 ?

[bethesque]

Yes, the bug looks correct. I don't know how to get that change into our codebase however. We might have to do some dirty hacks. We're in the process of moving off the Travelling Ruby package however, and replacing it with a Rust shared library. Would you be able to use a different directory in the meantime?

[Igor-Pchelko]

Yep, sure.

[TimothyJones]

@bethesque - would this diff be the workaround we'd need?

expo/expo-cli@920bb1a