fix(events): permit JFR Event Types without label attributes (backport #804) #805
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.
Welcome to Cryostat! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
To recreate commits with GPG signature
git fetch upstream && git rebase --force --gpg-sign upstream/main
Related to #803
Depends on cryostatio/cryostat-core#507
Description of the change:
JFR events do not necessarily have the
label
attribute, which in the JMC API is calledname
. The OpenJDK built-in events all happen to have this attribute, but custom application or framework events may not, and notably GraalVM has at least one event type (EveryChunkPeriodEvents
) which has no label.Motivation for the change:
Unlabelled JFR events would cause an NPE on
/api/v4/targets/{id}/events
query before this.How to manually test:
./mvnw -o clean package
./smoketest.bash -O -t quarkus-native
jmxquarkus
target. Ensure that Event Types table populates. Ensure that a recording can be started, archived, automated-analysis'd, etc.This is an automatic backport of pull request #804 done by [Mergify](https://mergify.com).