The custom reporter doesn't report errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- testing
Research direction
Start with src/intern/reporter.ts around the error event handler at line 83, where the custom Reporter is used instead of Intern's default reporter. Trace how fatal errors are handled and verify that the completed change reports them rather than allowing silent failures.
Written by the indexing model from the issue text.
Description
Bug
The custom Reporter class is used in place of Intern's default reporter, but doesn't actually report fatal errors in its error event handler (https://github.com/dojo/scripts/blob/master/src/intern/reporter.ts#L83). This can lead to silent failures.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
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.
More from dojo/scripts
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
dependencies
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
fix(errors): EHOSTUNREACH from a happy-eyeballs connect is reported as a resolver error (STAMP-80) Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
snapshot-labs/stamp#666 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GauravKarakoti/SecureFlow#1070 · 1 comment ·
-
feature:Languages/Translations good first issue ready Web
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
digitalfabrik/integreat-app#4394 ·