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

8167252: Some of Charset.availableCharsets() does not contain itself #14473

Closed
wants to merge 2 commits into from

Conversation

naotoj
Copy link
Member

@naotoj naotoj commented Jun 14, 2023

Adding themselves into their contains() method will fix it.


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-8167252: Some of Charset.availableCharsets() does not contain itself (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 14473

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

Using diff file

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

Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jun 14, 2023

👋 Welcome back naoto! 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 openjdk bot added the rfr Pull request is ready for review label Jun 14, 2023
@openjdk
Copy link

openjdk bot commented Jun 14, 2023

@naotoj The following labels will be automatically applied to this pull request:

  • i18n
  • nio

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

@openjdk openjdk bot added nio nio-dev@openjdk.org i18n i18n-dev@openjdk.org labels Jun 14, 2023
@mlbridge
Copy link

mlbridge bot commented Jun 14, 2023

Webrevs

Copy link
Member

@bplb bplb left a comment

Choose a reason for hiding this comment

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

Looks all right.

@openjdk
Copy link

openjdk bot commented Jun 14, 2023

@naotoj 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:

8167252: Some of Charset.availableCharsets() does not contain itself

Reviewed-by: bpb, alanb, iris, lancea, jpai

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 5 new commits pushed to the master branch:

  • 6b94289: 8309502: RISC-V: String.indexOf intrinsic may produce misaligned memory loads
  • 181845a: 8309899: Rename PtrQueueSet::buffer_size()
  • 931625a: 8309808: BytecodeTracer prints wrong BSM for invokedynamic
  • ee4ab67: 8309958: Incorrect @SInCE tag format in Container.java
  • 57b8251: 8309956: Shenandoah: Strengthen the mark word check in string dedup

Please see this link for an up-to-date comparison between the source branch of this pull request and 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 added the ready Pull request is ready to be integrated label Jun 14, 2023
Copy link
Contributor

@LanceAndersen LanceAndersen left a comment

Choose a reason for hiding this comment

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

Changes look fine over all.

It might be worth considering updating this to use junit at some point as a separate clean up activity as it could further streamline the test

@@ -103,6 +105,24 @@ static void checkUTF() throws Exception {
true);
}

static void selfContainmentTest() {
Copy link
Contributor

Choose a reason for hiding this comment

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

Be nice to add a comment regarding the purpose of the test

Copy link
Contributor

Choose a reason for hiding this comment

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

The spec is that Charset::contains return true for self so maybe it could be renamed to containsSelfTest, might help with the understanding the purpose (along with a comment)

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point. Will address these in the next iteration

Copy link
Member

@bplb bplb left a comment

Choose a reason for hiding this comment

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

Re-approved.

@jaikiran
Copy link
Member

Hello Naoto, should sun.util.PropertyResourceBundleCharset be fixed too? Its contains() currently just returns false. Then there is sun.font.X11Johab in java.desktop module whose contains() appears to have a typo and is checking against an unrelated X11GB18030_1 instance.

@AlanBateman
Copy link
Contributor

Hello Naoto, should sun.util.PropertyResourceBundleCharset be fixed too?

This is JDK internal, it shouldn't leak out via the APIs. If there is a way for it to leak out then it would require a compliant contains method but I suspect it's internal only.

@jaikiran
Copy link
Member

Hello Alan,

Hello Naoto, should sun.util.PropertyResourceBundleCharset be fixed too?

This is JDK internal, it shouldn't leak out via the APIs. If there is a way for it to leak out then it would require a compliant contains method but I suspect it's internal only.

You are right this is an internal class (I just found these by checking which classes extend Charset). I now paid a closer attention to the title of this issue and this is more about the Charset(s) that are returned through the public API, so I think it's OK to leave these internal classes as-is at least in this PR.

@naotoj
Copy link
Member Author

naotoj commented Jun 15, 2023

Thanks for the review, Jai.
As to PropertyResourceBundleCharset, yes it is an internal implementation as Alan mentioned, to auto detect UTF-8/ISO-8859-1, so even though contains() does not include itself, it is fine.

@naotoj
Copy link
Member Author

naotoj commented Jun 15, 2023

/integrate

@openjdk
Copy link

openjdk bot commented Jun 15, 2023

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

  • 653a8d0: 8310129: SetupNativeCompilation LIBS should match the order of the other parameters
  • 947f149: 8308444: LoadStoreNode::result_not_used() is too conservative
  • 8b4af46: 8309974: some JVMCI tests fail when VM options include -XX:+EnableJVMCI
  • 0038491: 8309978: [x64] Fix useless padding
  • 5f3613e: 8309960: ParallelGC young collections very slow in DelayInducer
  • 83d9267: 8303513: C2: LoadKlassNode::make fails with 'expecting TypeKlassPtr'
  • de8aca2: 8307907: [ppc] Remove RTM locking implementation
  • 4c0e164: 8309717: C2: Remove Arena::move_contents usage
  • 6b94289: 8309502: RISC-V: String.indexOf intrinsic may produce misaligned memory loads
  • 181845a: 8309899: Rename PtrQueueSet::buffer_size()
  • ... and 3 more: https://git.openjdk.org/jdk/compare/955fc2fabafc4c4d79d137bf86194228d5cf8ad8...master

Your commit was automatically rebased without conflicts.

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

openjdk bot commented Jun 15, 2023

@naotoj Pushed as commit 3eeb681.

💡 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
i18n i18n-dev@openjdk.org integrated Pull request has been integrated nio nio-dev@openjdk.org
Development

Successfully merging this pull request may close these issues.

6 participants