Yield UnsupportedMessageException
when context isn't accessible
#11334
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.
Pull Request Description
More robust fix for #11127 as it turns out #11241 is insufficient.
Important Notes
@radeusgd has observed yet another error related to lazy evaluation of
computeMessage
:even the handleRun tries to "force computation of the exception message sooner than context is closed" it is still not enough. Let's make the
PanicException
more robust.Anyway, the real problem is escaping panic exception and it has been reported to GraalVM.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Java,