Change level of initialization exception to error, make errors obvious #29078
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.
Exceptions in JvmInitializers were being printed in the STDOUT by the FnHarness, so handled/displayed on Dataflow as an info log:
This change should help making errors more obvious, and allow users to leverage Error Reporting.
I still kept
e.printStackTrace();
in case there was someone relies on looking at errors on STDOUT/STDERR (happy to remove if seen as a bad practice).