Potential threading issue
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.8k
- Forks
- 704
- PR merge metrics
- No merged PRs in 30d
Description
If I try to clone or fetch multiple projects at the same it seems to fail silently sometimes, leaving the promise unresolved forever. I'm testing against a remote repo using the SSH protocol.
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 concurrent clone or fetch operations against an SSH remote and observe whether a promise remains unresolved. Trace the clone/fetch entry points and SSH-related handling in NodeGit, then compare concurrent and single-operation behavior. Done means failures are reported or operations complete rather than silently leaving promises unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, node.js
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100