-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
chore(developer): resolve excessive-fatal-exception issue #10949
Conversation
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
To my mind, the fatal error is something that is a bug in our compiler. We want to know about it, which is what is happening. It's kinda hard to write a test for this because if we knew what was causing the fatal error, we should be fixing the fatal error instead |
Fixing the fatal error might require restructuring callbacks and is discussed in #10894 |
I'm not seeing the restructure discussion? |
- remove the fatal exception about a failed section compiler, as it will always otherwise be propagated to the user Fixes: #10894
b7c7f48
to
e77a495
Compare
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.
LGTM
Does this close the original issue? |
Changes in this pull request will be available for download in Keyman version 17.0.287-beta |
#10894
@keymanapp-test-bot skip