mandatoryprogrammer / mandatoryprogrammer/xsshunter-express
exited with code 127 in windows
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.4k
- Forks
- 428
- PR merge metrics
- No merged PRs in 30d
Description
Attaching to xsshunter-express_xsshunterexpress_1
xsshunterexpress_1 | /usr/bin/env: 'bash\r': No such file or directory
xsshunter-express_xsshunterexpress_1 exited with code 127
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's container startup configuration and the shell entry point that produces the `/usr/bin/env: 'bash\r'` error. Reproduce the setup on Windows and check how line endings are handled. Done means the container starts successfully without exiting with code 127.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, javascript
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100