question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Working directory path with space and parentheses

See original GitHub issue

I have an similar issue to this https://github.com/broadinstitute/cromwell/issues/1306, but I don’t think OP’s solution fits whats going in my case since input files are not part of the issue.

Using the hello-world example:

task hello {
  String name

  command {
    echo 'Hello ${name}!'
  }
  output {
    File response = stdout()
  }
}

workflow test {
  call hello
}

with input

{
  "test.hello.name": "World"
}

I run $ cromwell run hello.wdl hello.json hello.out

I get the error message:

/Users/jasonweirather/Dropbox (Partners HealthCare)/projects/2017_08_FIRECLOUD/cromwell-executions/test/12ed39b6-cf8f-4ea1-a965-193cd89f99e9/call-hello/execution/stderr.background -bash: syntax error near unexpected token `(’

Seems it may be having troubles being run from a working directory with a space and parentheses.

This was done on Mac OS X 10.12.6 in the bash terminal. Version of cromwell is cromwell: 28-5fd2237-SNAP

Issue Analytics

  • State:open
  • Created 6 years ago
  • Reactions:1
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
jason-weirathercommented, Feb 26, 2020

@mcovarr Ran into this again. Not sure how a “User Requested Improvement” sits it in your planning, but I’d suggest this be considered as a bug, not a quality of life thing. I think proper path handling on supported operating systems should be standard, and hopefully not a big lift for a team like yours. Thanks!

0reactions
yfarjouncommented, Oct 18, 2021

@mcovarr your workaround doesn’t work for me (in osx). I’m in a linked directory, but the code will use the non-linked, i.e. with space, path…

Read more comments on GitHub >

github_iconTop Results From Across the Web

Spaces and Parenthesis in windows PATH variable screws up ...
Directory in path that is properly escaped with quotes, and has spaces and has a parenthesis = ERROR. Whats going on here? How...
Read more >
Passing a path that contains spaces and parentheses to ...
I am currently writing a script where I have to call MATLAB from the Terminal and pass it a path argument that contains...
Read more >
Change directory with space followed by '('
You have to escape the parentheses: ... Another way to accomplish the same is to quote the path containing whitespace:
Read more >
Characters to Avoid in Filenames and Directories
Don't start or end your filename with a space, period, hyphen, or underline. Keep your filenames to a reasonable length and be sure...
Read more >
Is it bad practice to put parentheses in a file name? - Quora
On POSIX shells, you'll need to quote or escape strange characters like parenthesis or spaces in file names. It is boring and error...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found