-
Notifications
You must be signed in to change notification settings - Fork 30
update to verror 1.7.0. call captureStackTrace manually. #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fdd3daf to
6987978
Compare
| "eslint": "^3.0.1", | ||
| "istanbul": "^0.4.2", | ||
| "jscs": "^3.0.7", | ||
| "jscs": "^2.11.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason 3.x seems to be crashing on me locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sure your global version of jscs is updated to 3.x. That's what fixed it for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But the makefile isn't calling the global jscs? Shouldn't make a diff.
| // will handle calling captureStackTrace, using arguments.callee to | ||
| // eliminate unnecessary stack frames. | ||
| WError.apply(self, args); | ||
| Error.captureStackTrace(self, HttpError); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we have to do this explicitly now? Is this part of the new VError API?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The underlying API changed - check out the linked issue in the PR for more info (I filed an issue over with VError).
|
Closing in favor of #53 since this was fixed in new verror patch release. |
Fixes stack frames that weren't being elided due to new WError constructor in verror@1.7.0. More details over in TritonDataCenter/node-verror#39.