-
Notifications
You must be signed in to change notification settings - Fork 40
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
1.3.0-99: Windows: "Pipeline failed: source" on 2nd+ run #322
Comments
Thanks, @AirQuick . I've reproduced it on Windows. I'm at a loss to explain why it's Windows specific, but I've had "get my Windows dev environment functioning" on my todo list for a couple of weeks. The bug is in Apologies for the inconvenience. |
The backslashes look like usual suspects to me, here ;-) |
Out of curiousity, @AirQuick what shell are you using on Windows? If it's not 'Command Prompt' can you try it with that shell and see if you get different results? |
#322 (comment) was on PowerShell, but it's reproduced also on Command Prompt. |
Fixed in 1.3.1. |
Verified the fix. Thanks! |
Depending on
.xmlresolver
dir, 1.3.0-99 fails withERROR: Pipeline failed: source
on Windows 10. Not repro on Ubuntu 18.04.The error has not happened on 1.2.5-99.
Clone XSpec v2.1.4 and
cd
to it:Make sure you don't have
.xmlresolver
dir in your user profile dir.Run
src\harnesses\saxon\saxon-xquery-harness.xproc
(-p xspec-home=
must point the directory URI where XSpec is cloned). It works:Now you have
.xmlresolver
dir in your user profile dir.Run
src\harnesses\saxon\saxon-xquery-harness.xproc
again with the exact same command line. This time it doesn't work:Remove
.xmlresolver
dir from your user profile dir.Run
src\harnesses\saxon\saxon-xquery-harness.xproc
with the exact same command line. It works again.The text was updated successfully, but these errors were encountered: