| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@legendecas is there any related issue or additional context? |
Sorry, something went wrong.
No, I didn't find any issues raised. Please checkout the tests included in the PR. Basically the issue is that node-report is unable to print those thrown primitives as uncaught exceptions. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Just pushed with rebase and a fix on crash with V8_ENABLE_CHECKS flag. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Looks like the CI failures are produced on pi2-docker, mostly "warning: failed to remove out/Release/.nfs00000000018426c4000015ac: Device or resource busy". And the history looks like the failure is happening to start from days ago. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #38009 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
PR-URL: #38009 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
PR-URL: #38009 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
| Back | FazBrowse Home | New Git URL |
Any JavaScript values can be thrown and they have to be printed in node-report to prevent confusion.
This PR is trying to print primitive values' ToString value in the report as the javascriptStack.message.