ReferenceError: res is not defined
Open
- Dominant language
- Ruby
- Stars
- 548
- Forks
- 168
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 22
Description
## Error
```
res is not defined
```
## Stack trace
```
/80c7ea41-af61-4393-8f5b-fe5fd86d1efd:63 in allSettled/Proc/
Contributor guide
Research direction
Start with the linked Sentry report and its stack trace, then trace the exercism-js execution path identified as allSettled/Proc. Determine where the undefined res reference originates and verify the error no longer occurs; the issue names no source file or test, so the relevant regression coverage must be located first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100