-
Notifications
You must be signed in to change notification settings - Fork 30k
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
[v14.x-backport] report: generates report on threads with no isolates #39515
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
c++
Issues and PRs that require attention from people who are familiar with C++.
needs-ci
PRs that need a full CI run.
report
Issues and PRs related to process.report.
v14.x
labels
Jul 25, 2021
legendecas
requested review from
cjihrig,
gireeshpunathil and
himself65
and removed request for
cjihrig and
gireeshpunathil
July 25, 2021 16:42
legendecas
force-pushed
the
backport-to-14/38994
branch
from
July 25, 2021 16:47
bfb6773
to
60b98e8
Compare
legendecas
added
node-api
Issues and PRs related to the Node-API.
and removed
node-api
Issues and PRs related to the Node-API.
labels
Jul 26, 2021
richardlau
force-pushed
the
v14.x-staging
branch
from
July 29, 2021 16:40
073941c
to
0061e5d
Compare
Can you please rebase? |
BethGriggs
force-pushed
the
v14.x-staging
branch
from
August 12, 2021 16:49
78bb65e
to
73e6781
Compare
ping @legendecas |
legendecas
force-pushed
the
backport-to-14/38994
branch
from
August 30, 2021 16:08
60b98e8
to
550f5d9
Compare
@targos updated! :) |
MylesBorins
force-pushed
the
v14.x-staging
branch
from
August 31, 2021 14:58
b3f51ee
to
327838d
Compare
napi_fatal_error and node watchdog trigger fatal error but rather running on a thread that hold no current isolate. PR-URL: nodejs#38624 Reviewed-By: Michael Dawson <midawson@redhat.com>
PR-URL: nodejs#38994 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
targos
force-pushed
the
backport-to-14/38994
branch
from
September 1, 2021 17:33
550f5d9
to
3cab19c
Compare
Landed in a74032a...f69c934 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This backport contains following commits:
report: generates report on threads with no isolates
PR-URL: #38994
Reviewed-By: Gireesh Punathil gpunathi@in.ibm.com
Reviewed-By: Anna Henningsen anna@addaleax.net
Reviewed-By: James M Snell jasnell@gmail.com
src: fix fatal errors when a current isolate not exist
napi_fatal_error and node watchdog trigger fatal error but rather
running on a thread that hold no current isolate.
PR-URL: #38624
Reviewed-By: Michael Dawson midawson@redhat.com