Avoid UB in installer and check manifest data in advance #1628
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.
In the latest release of Trials, modifying the forge installer jar file may corrupt the manifest data, exposing a potential issue of relying on an undefined order of ServiceLoader.load(...).stream() between different modules in the same layer.
The issue will cause a conditional crash that depends on the archive file name when the installer is modified externally. The module name will also be related to the file name.
In this PR: