-
Notifications
You must be signed in to change notification settings - Fork 57
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
@params.txt parsing is various types of broken #250
Comments
Can you show the whole command line you are using? Those failures look a bit like what I would expect if the parameters are inserted after the script file rather than before. The general form has to be:
Can you confirm that your form follows the above? |
I can confirm I'm running it that way:
|
Moving the -n300 had the same result |
Very strange, I can't pick what's wrong. The reading of the parameters from the file is being done under the hood by the same library that parses the command arguments (not Bpipe doing that explicitly). The behavior of that library is that it literally takes whatever is in the file and injects it as command line arguments. So it ought to work if the contents of your file is like:
Note the Obviously, it's critical that there are no spaces or anything that would count as a space in there. Otherwise, I'm not sure what's wrong! |
NB: it would be interesting to know if this test passes for you: https://github.com/ssadedin/bpipe/tree/master/tests/params_from_file It is not demonstrating ideal usage (the |
|
Hmm, that's a problem, but not the one I expected! Just checking the obvious, did you build the code yet? As in, in the top level directory:
|
I used my bpipe install 0.9.9.6 which has been functioning for me and the 20+ folks who use my pipelines written in bpipe otherwsie :) |
0.9.9.7 release has the same bug. In case it may be relevant:
|
Following up here. Cloning master and building bpipe from source results in a the test passing, so I'm learning towards this bug being an issue with the bpipe distribution version (+ maybe an interaction with my java) |
Hi, just following up again. The downloadable bpipe version is broken, but if I build locally these tests work. Any ideas why? |
Followup here. The test passes for 0.9.9.7. If I use the "recommended format"
Fails with error:
If instead I setup like the test:
And run like the test:
We get success:
|
Hi, I'm following up again here because I would like to change my pipeline to use configuration file options but I am not comfortable doing so until the difference between the docs and the functional implementation is resolved. The working version (and the in-repo test code) uses -p@params.txt while the documentation specifies @params.txt directly. Which is considered correct? If the later, it is broken during use. |
Followup here, documentation is still unclear. |
I'm trying to move my variables defined at the top of pipeline into a config file so I can offer differently configured versions.
At first glance, I expected to be able to just move the variables into a file and add "-p" to the front, and everything would go.
So, a variable defined like this:
Fails:
Changing to the bash style:
Still fails:
Changing it to a real path:
Still fails with java errors:
The text was updated successfully, but these errors were encountered: