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
pact-node fails to launch mock server on windows #90
Comments
Hmm could you please share your Windows environment details? Which shell are you running it on? |
@bbarke was there any issues with your install process? There's a postinstall that runs and downloads the binary files needed for your OS. Maybe just try to reinstall it using |
This is on Windows 10 with the regular windows terminal. It looks like the issue was because the location/path of the project had a space in it, for example:
|
@bbarke wait, pact-node didn't work because of the space or just the .bat command? Because if it's the former, there's definitely an issue which shouldn't happen. Can you please confirm? |
Yes I can confirm this. I renamed a working pact project path to have a space in it, and pact failed to launch. I changed the name back to to not have a space, and it started working again. |
@bbarke my question is, are you talking about using the command line to hit the .bat file, or using the pact-node CLI/API? Because if it's the latter, that's a bug that needs to be fixed. |
I'm using karma-pact, which uses the node CLI/API to start the pact stub server. |
huh, okay. This might be a bug then. I'll have to investigate further,
but I'm guessing it has something to do with the shell script running that
wrapping it in quotes.
…On Thu, May 10, 2018 at 9:44 AM Brent Barker ***@***.***> wrote:
I'm using karma-pact, which uses the node CLI/API to start the pact stub
server.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjA5EtTjiYxoIcoLnD1R6eD0v7YVb03ks5tw39MgaJpZM4T1vcy>
.
|
@mboudreau, if quoting is indeed the issue, then the investigation here might be useful: pact-foundation/pact-js#160 |
Yep, spot on. I'll fix this today if I can.
…On Thu., 10 May 2018, 11:49 am Timothy Jones, ***@***.***> wrote:
@mboudreau <https://github.com/mboudreau>, if quoting is indeed the
issue, then the investigation here might be useful:
pact-foundation/pact-js#160
<pact-foundation/pact-js#160>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjA5PPSF0SPMF8kAbN7RimpiB_GiKOPks5tw5zAgaJpZM4T1vcy>
.
|
@bbarke very sorry I haven't gotten to this yet. It's been hectic at work with GDPR :/ |
@bbarke good news, version 6.18.3 is going out as we speak with the windows path fixes. Please let us know how you go. Cheers. |
Thanks Michel! |
Thank you! |
We are using pact-node (v6.16.0) bundled with pact-karma (2.1.5) and pact-web (5.9.0)
When trying to run the pact tests on a windows machine, I'm seeing the following error
When trying to run that bat file directly, I get the following error
Any pointers on why this is happening?
The text was updated successfully, but these errors were encountered: