-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8325945: Error reporting should limit the number of String characters printed #20150
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
Conversation
👋 Welcome back dholmes! A progress list of the required criteria for merging this PR into |
@dholmes-ora 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 66 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 |
@dholmes-ora 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.
Looks good to me otherwise. Thanks for fixing this!
Thanks for the review @TobiHartmann |
I've updated per Thomas's suggestion to show the number of characters omitted. However I kept the " (abridged)" part as well as with actual very long strings you are more likely to spot that at the end than the "... (N characters ommitted) ..." in the middle. |
|
||
if (length > max_length) { | ||
st->print(" (abridged) "); | ||
} |
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.
Do we still need this marker?
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.
See my comment above:
#20150 (comment)
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.
Oh that makes sense. Okay!
"in the VM. If exceeded, an abridged version of the string is " \ | ||
"printed with the middle of the string elided.") \ | ||
range(2, O_BUFLEN) \ | ||
\ |
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.
This would make sense as a product diagnostic switch. You want to be able to increase this at a customer if needed.
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.
This is modelled after the MaxElementPrintSize
that precedes it.
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.
Looks good.
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.
Still looks good to me.
Thanks for the reviews! /integrate |
Going to push as commit 10fcad7.
Your commit was automatically rebased without conflicts. |
@dholmes-ora Pushed as commit 10fcad7. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
runtime/PrintingTests/StringPrinting.java fails with release VMs. |
Please review this enhancement that intends to improve the readability of error logs when very long
java.lang.String
s exist and when printed in full they obscure things in the log.The suggestion was to add a
MaxStringPrintSize
flag, similar to theMaxElementPrintSize
for arrays. I've set the default to 256 (arbitrary selection: not too big, not too small - may need adjusting) with a range from 2 to O_BUFLEN.The method
java_lang_String::print
now takes amax_length
parameter that defaults toMaxStringPrintSize
. This allows more direct control if specific call sites want to print full strings regardless.If a string's length exceeds
max_length
then we print it as follows:For example if we print "ABCDE" with a max_length of 4 then the output is literally:
The message doesn't mention
MaxPrintStringSize
as that may not be involved in limiting the printed length. Developers will need to know to look at that (which is not 100% satisfactory but explaining everything in the output itself seems a bit excessive).For testing purposes I added a WhiteBox API to print the string to a
stringStream
and then return it as a newjava.lang.String
.Testing:
Thanks
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/20150/head:pull/20150
$ git checkout pull/20150
Update a local copy of the PR:
$ git checkout pull/20150
$ git pull https://git.openjdk.org/jdk.git pull/20150/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 20150
View PR using the GUI difftool:
$ git pr show -t 20150
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/20150.diff
Webrev
Link to Webrev Comment