-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8261269: When using clhsdb to "inspect" a java object, clhsdb prints "Oop for..." twice #2582
Conversation
👋 Welcome back cjplummer! A progress list of the required criteria for merging this PR into |
@plummercj The following label will be automatically applied to this pull request:
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. |
Webrevs
|
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.
It looks good to me.
One side comment about the test. It is not easy to read the code with the same pattern (e.g. "Oop for java/io/BufferedInputStream") repeated several times. I understand, you prefer to make it more explicit but it'd be more readable if a predefined pattern is used like below:
String pattern = "Oop for java/io/BufferedInputStream";
+ expStrMap.put(cmd, List.of("instance of Oop for java/lang/Class @ " + examineResult,
+ "in: " + pattern + @"));
. . .
+ unexpStrMap.put(cmd, List.of(
+ "instance of Oop for java/lang/Class @ " + examineResult + " @ " + examineResult,
+ "in: " + pattern + " .* " + pattern));
Just an opinion with no pressure. It is up to you.
Thanks,
Serguei
@plummercj 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:
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 81 new commits pushed to the
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 |
Good idea. I've added the pattern strings. Thanks! |
That's great, much more readable output! |
Thanks Serguei and Kevin! |
/integrate |
@plummercj Since your change was applied there have been 90 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit aea474c. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
See CR for details. In brief, fixed the
inspect
command to remove duplicate output:It should be:
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2582/head:pull/2582
$ git checkout pull/2582