Skip to content
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

Fix problem with whitespaces in cwd #41

Closed
wants to merge 1 commit into from

Conversation

epszaw
Copy link
Member

@epszaw epszaw commented Feb 1, 2024

fixes #30

@epszaw epszaw force-pushed the issue-30-fix-cwd-whitespaces-support branch from cce7873 to a1355db Compare February 1, 2024 15:40
@epszaw epszaw requested a review from baev February 1, 2024 15:40
@baev
Copy link
Member

baev commented Feb 1, 2024

$ git clone git@github.com:allure-framework/allure-npm.git "allure npm"
$ cd allure\ npm
$ git checkout issue-30-fix-cwd-whitespaces-support
$ ./fetch-source.sh
$ node bin/allure --version

produces the following error


ode:events:492
      throw er; // Unhandled 'error' event
      ^

Error: spawn "/Users/baev/projects/allure npm/dist/bin/allure" ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:292:12)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn "/Users/baev/projects/allure npm/dist/bin/allure"',
  path: '"/Users/baev/projects/allure npm/dist/bin/allure"',
  spawnargs: [ '--version' ]
}

Node.js v20.9.0

@baev baev closed this Feb 1, 2024
@baev baev deleted the issue-30-fix-cwd-whitespaces-support branch February 1, 2024 17:24
@studioromeo
Copy link

@baev is there another PR where this work was continued? I'm confused why this PR was closed and wondered if you wouldn't mind someone picking it up again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Command does not work with path containing white-space
3 participants