Uncaught exceptions on hex char been deliverd to verror.js
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 144
- Forks
- 30
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
when creating new restify error with a "%25" as a prefix and than one of the following chars (e,E,f,g,G,d etc...) the application will break with an uncaught exception.
it looks like verror uses sprintf, and it encodes "%25" a real "%" delivered as an argument.
this end with "Error: next shouldn't be called more than once"
Contributor guide
No contributing guide indexed for this repository
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 the failure described when creating a Restify error with a "%25" prefix followed by a format-like character. Inspect how verror.js uses sprintf and how the escaped percent is passed as an argument. Done means the application no longer raises the uncaught "next shouldn't be called more than once" exception for these inputs, with regression coverage for the reported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100