-
Notifications
You must be signed in to change notification settings - Fork 130
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
jfr-connection: jfr-connection: wrong parameter sent to JFR DiagnosticCommand #1492
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some tests are failing now.
Could you please have a look?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @dsgrieve!
It looks generally good to me.
.../java/io/opentelemetry/contrib/jfr/connection/FlightRecorderDiagnosticCommandConnection.java
Outdated
Show resolved
Hide resolved
.../java/io/opentelemetry/contrib/jfr/connection/FlightRecorderDiagnosticCommandConnection.java
Outdated
Show resolved
Hide resolved
.../java/io/opentelemetry/contrib/jfr/connection/FlightRecorderDiagnosticCommandConnection.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @dsgrieve!
Description:
Change parameter used with JFR DiagnosticCommand from "name" to "recording" since it is the recording id that jfr-connection uses to identify JFR recordings.
Existing Issue(s):
1491
Testing:
Functionality already covered by existing tests
Documentation:
No documentation changes required.
Outstanding items:
None.