di-sukharev / di-sukharev/opencommit
[Bug]: `uv_tty_init returned EBADF` on Windows
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Opencommit Version
2.4.2
Node Version
18.17.0
NPM Version
9.6.7
What OS are you seeing the problem on?
Windows
What happened?
Your cli seems to suffer from the same malady Nutlope/aicommits once did pertaining to Windows file descriptors:
◇ 📝 Commit message generated
25h│
└ ✖ TTY initialization failed: uv_tty_init returned EBADF (bad file descriptor)
They resolved it like so: https://github.com/Nutlope/aicommits/pull/176
Expected Behavior
To not throw an error
Current Behavior
It throws uv_tty_init returned EBADF
Possible Solution
https://github.com/Nutlope/aicommits/pull/176
Steps to Reproduce
Run oco in a repo on a Windows machine
Relevant log output
◇ 📝 Commit message generated
│
└ ✖ TTY initialization failed: uv_tty_init returned EBADF (bad file descriptor)
Contributor guide
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 reproducing oco in a repository on Windows with the reported Opencommit, Node, and npm versions. Compare the TTY failure with the linked Nutlope/aicommits issue and pull request; done means commit-message generation completes without uv_tty_init returned EBADF.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100