| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
CI is all green except flaky tests and CI issues: https://ci.nodejs.org/job/node-test-pull-request/1001/ |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Using the normal workflow, this will cause two arrow messages to be printed. For example: $ node foo.js /Users/cjihrig/iojs/node/foo.js:1 ^ ^ /Users/cjihrig/iojs/node/foo.js:1 ^ ^ SyntaxError: Unexpected token ^ ... Where foo.js just contains a ^. |
Sorry, something went wrong.
|
From a quick test, it looks like removing the arrow information from ReportException() in node.cc fixes the problem. |
Sorry, something went wrong.
|
Hrmm... what about adding/checking a "decorated" flag as another hidden value on the error object? |
Sorry, something went wrong.
|
@cjihrig Alright, I added a 'decorated' flag and a new test for uncaught errors. CI is all green except flaky tests/CI issues: https://ci.nodejs.org/job/node-test-pull-request/1006/ |
Sorry, something went wrong.
There was a problem hiding this comment.
Should this use result?
Sorry, something went wrong.
There was a problem hiding this comment.
Fixed.
Sorry, something went wrong.
|
Incorporated suggestions and CI is green except flaky tests: https://ci.nodejs.org/job/node-test-pull-request/1010/ |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
There was a problem hiding this comment.
I'd probably give this a slightly more unique name, e.g. 'node:decorated'. (Ditto for 'arrowMessage' although this PR didn't introduce that.)
Sorry, something went wrong.
|
semver-minor? |
Sorry, something went wrong.
|
@bnoordhuis I've made your suggested changes. LGTY now? |
Sorry, something went wrong.
There was a problem hiding this comment.
Superfluous parentheses and you can shorten it to return !decorated.IsEmpty() && decorated->IsTrue(), which should also be infinitesimally faster.
Sorry, something went wrong.
|
LGTM with a nit and a suggestion. |
Sorry, something went wrong.
This provides more information when encountering a syntax or similar error when executing a file with require().
|
Updated commit. Last CI run: https://ci.nodejs.org/job/node-test-pull-request/1022/ |
Sorry, something went wrong.
|
@jasnell I'm not sure how this fits in (if at all) with whatever was agreed upon on with regard to changing errors and semver-ness, but my guess would be semver-major since it's changing the formatting of the stack trace? |
Sorry, something went wrong.
This provides more information when encountering a syntax or similar error when executing a file with require(). Fixes: nodejs#4286 PR-URL: nodejs#4287 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Notable changes: * general: Several minor performance improvements: - lib: Use arrow functions instead of bind where possible (Minwoo Jung) nodejs#3622 - node: Improved accessor perf of process.env (Trevor Norris) nodejs#3780 - **node**: Improved performance of hrtime() (Trevor Norris) nodejs#3780 - node: Improved GetActiveHandles performance (Trevor Norris) nodejs#3780 * module: Errors during require() now provide more information (Brian White) nodejs#4287
|
Marking as semver-major due to the error handling change. It's not clear if this is major or minor tho. @nodejs/ctc |
Sorry, something went wrong.
This provides more information when encountering a syntax or similar error when executing a file with require(). Fixes: nodejs#4286 PR-URL: nodejs#4287 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
| Back | FazBrowse Home | New Git URL |
This provides more information when encountering a syntax or similar error when executing a file with require().