Skip to content

Conversation

@egahlin
Copy link
Member

@egahlin egahlin commented Apr 17, 2025

Could I have a review of a PR that cleans up the EventInstrumentation class and moves the non-modifying parts into a separate class (ClassInspector)?

I deleted the code that removes the instrumentation (buildUninstrumented), because it has never been used. If there should be a need for it in the future, it's not hard to add code that inserts empty method bodies.

Testing: tier1 + jdk/jdk/jfr/test

Thanks
Erik


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8354949: JFR: Split up the EventInstrumentation class (Enhancement - P3)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24726/head:pull/24726
$ git checkout pull/24726

Update a local copy of the PR:
$ git checkout pull/24726
$ git pull https://git.openjdk.org/jdk.git pull/24726/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 24726

View PR using the GUI difftool:
$ git pr show -t 24726

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24726.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 17, 2025

👋 Welcome back egahlin! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Apr 17, 2025

@egahlin This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8354949: JFR: Split up the EventInstrumentation class

Reviewed-by: mgronlun, liach

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 62 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot changed the title 8354949 JFR: Split up the EventInstrumentation class 8354949: JFR: Split up the EventInstrumentation class Apr 17, 2025
@openjdk
Copy link

openjdk bot commented Apr 17, 2025

@egahlin The following label will be automatically applied to this pull request:

  • hotspot-jfr

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the hotspot-jfr hotspot-jfr-dev@openjdk.org label Apr 17, 2025
@egahlin egahlin marked this pull request as ready for review April 17, 2025 15:47
@openjdk openjdk bot added the rfr Pull request is ready for review label Apr 17, 2025
@mlbridge
Copy link

mlbridge bot commented Apr 17, 2025

Webrevs

private List<AnnotationValue> getAnnotationValues(ClassDesc classDesc) {
List<AnnotationValue> list = new ArrayList<>();
for (Attribute<?> attribute: classModel.attributes()) {
if (attribute instanceof RuntimeVisibleAnnotationsAttribute rvaa) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

findAttribute or findAttributes can be helpful if you just want one attribute.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, but I like to refactor that in a later PR. That part of the code needs a complete rewrite.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Apr 22, 2025
Copy link
Member

@liach liach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ClassFile API usages look good.

@egahlin
Copy link
Member Author

egahlin commented Apr 23, 2025

Thanks for the reviews.

/integrate

@openjdk
Copy link

openjdk bot commented Apr 23, 2025

Going to push as commit ef0cd18.
Since your change was applied there have been 87 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Apr 23, 2025
@openjdk openjdk bot closed this Apr 23, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Apr 23, 2025
@openjdk
Copy link

openjdk bot commented Apr 23, 2025

@egahlin Pushed as commit ef0cd18.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot-jfr hotspot-jfr-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants