plugin bug/misbehavior can lead to silent exit (also see #606 )
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 26.3k
- Forks
- 1.8k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 20
Description
- Rollup Version: any
- Operating System (or Browser): Linux
- Node Version (if applicable):
- Link to reproduction (IMPORTANT, read below): https://repl.it/@pkit/async-no-resolve
Expected Behavior
Timeout
Actual Behavior
Silent exit, see #606
Need to add a race with timeout and some sort of a listener queue.
Otherwise it will just exit on any buggy plugin code. And people cannot be expected to be able to debug each and every plugin for potential misbehavior.
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 running the linked reproduction at https://repl.it/@pkit/async-no-resolve and compare its silent exit with the expected timeout; also review the related issue #606. The issue proposes a timeout race and listener queue, but names no source files or tests. Done means buggy plugin behavior results in a timeout or reported failure rather than a silent exit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100