adobe / adobe/aio-cli-plugin-app

`aio app test` is failing on EBADF bad file descriptor (Windows only)

Open
#372 8 comments 0 reactions 1 assignee Claimed by @shazron View on GitHub
bug
Dominant language
JavaScript
Stars
28
Forks
41
Avg merge
1d 2h
Merged PRs (30d)
3

Description

### Expected Behaviour
On Windows i expect to be able to test my firefly application by running the command `aio app test`

### Actual Behaviour
Crash
```
`D:\code\2021\git\demos\gettingstarted>aio app test
child_process.js:114
p.open(fd);
^

Error: EBADF: bad file descriptor, uv_pipe_open
at Object._forkChild (child_process.js:114:5)
at setupChildProcessIpcChannel (internal/bootstrap/pre_execution.js:328:30)
at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:49:3)
at internal/main/run_main_module.js:7:1 {
errno: -4083,
code: 'EBADF',
syscall: 'uv_pipe_open'
}
» Error: Command failed with ENOENT: jest --passWithNoTests ./test
» spawn jest ENOENT`
```
### Reproduce Scenario (including but not limited to)
aio app init getting started
Adobe IO Demo org
default options the rest of the way

#### Steps to Reproduce

#### Environment Info
```
System:
OS: Windows 10 10.0.19042
CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Memory: 23.78 GB / 47.91 GB
Binaries:
Node: 12.13.0
Yarn: 1.22.5
npm: 6.12.0
Virtualization:
Docker: 20.10.2
npmGlobalPackages:
@adobe/aio-cli: Not Found
```
#### Sample Code that illustrates the problem

#### Logs taken while reproducing problem

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.