Skip to content
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

Point out that PR needs to remove GraalVM reachability metadata related to MBeans #135

Closed
wants to merge 1 commit into from

Conversation

linghengqian
Copy link
Contributor

@linghengqian linghengqian commented Dec 2, 2022

What does this PR do?

Checklist before merging

  • I have properly formatted metadata files (see CONTRIBUTING document)
  • I have added thorough tests. (see this)

@linghengqian linghengqian mentioned this pull request Dec 9, 2022
2 tasks
@@ -122,6 +122,19 @@ output if necessary:
./gradlew check
```

All submitted GraalVM reachability metadata, if the MBean-related part is unnecessary, should actively remove the
Copy link
Member

Choose a reason for hiding this comment

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

We should fix the root cause in Native Image. Could you be more precise about what is failing if we introduce MBean metadata?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@vjovanov
Copy link
Member

We need to fix this on the GraalVM side: no extra metadata should change the correct functionality. It would be best to open an issue on the GraalVM repo with a small reproducer.

@vjovanov vjovanov closed this Mar 23, 2023
@linghengqian linghengqian deleted the markdown branch March 23, 2023 17:53
Copy link
Contributor Author

@linghengqian linghengqian left a comment

Choose a reason for hiding this comment

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

  • @vjovanov I never reproduced this issue reported by the Spring team, which seems to have to use Spring Boot to write a relatively complex Example.

  • @wilkinsona I wonder if there are some reproducible unit tests on the Spring side?

@wilkinsona
Copy link
Contributor

I don't think there's anything Spring or Spring Boot-specific about the problem. It will be harder to reproduce now after the corrections to the metadata. Please open the requested GraalVM issue and I'll help out there as time permits. IMO, linking to spring-projects/spring-boot#33210 would be a good start.

@wilkinsona
Copy link
Contributor

I should also have said that, while I agree that this should be fixed on the Graal side, I don't think metadata contributions should include anything for types like com.sun.management.GarbageCollectorMXBean which they never even touch irrespective of whether or not that cause a failure. If this PR has been declined, what alternative measures can we put in place to prevent future metadata updates causing problems or being too broad in scope?

@vjovanov
Copy link
Member

We have a check now that makes sure that all conditions in the metadata are related to the library in question. This way, all unintentional metadata additions of this kind should be avoided.

@wilkinsona
Copy link
Contributor

Great stuff! Thank you.

@linghengqian
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

In CONTRIBUTING.md point out that PR needs to remove GraalVM reachability metadata related to MBeans
3 participants