From jpai at openjdk.org Thu Sep 1 06:32:04 2022 From: jpai at openjdk.org (Jaikiran Pai) Date: Thu, 1 Sep 2022 06:32:04 GMT Subject: RFR: 8293008: Replace uses of StringBuffer with StringBuilder in MergeCollation [v2] In-Reply-To: References: Message-ID: On Wed, 31 Aug 2022 08:40:29 GMT, Andrey Turbanov wrote: >> src/java.base/share/classes/java/text/PatternEntry.java line 55: >> >>> 53: * Gets the current extension, quoted >>> 54: */ >>> 55: public void appendQuotedExtension(StringBuilder toAddTo) { >> >> Hello Andrey, this and the other `public` method that's changed in this (package private) class don't seem to be used anywhere else other than this class itself. So maybe you could change them to `private` as part of this change? > > Changed a few of methods to `private` Thank you Andrey for doing those changes. ------------- PR: https://git.openjdk.org/jdk/pull/10007 From naoto at openjdk.org Thu Sep 1 15:49:17 2022 From: naoto at openjdk.org (Naoto Sato) Date: Thu, 1 Sep 2022 15:49:17 GMT Subject: Integrated: 8293154: TemporalQueries java doc error In-Reply-To: References: Message-ID: On Wed, 31 Aug 2022 17:08:28 GMT, Naoto Sato wrote: > Simple doc fix. This pull request has now been integrated. Changeset: 6a1b0b56 Author: Naoto Sato URL: https://git.openjdk.org/jdk/commit/6a1b0b5649dd4f2a970df0839bf77bdb899fbd6f Stats: 3 lines in 1 file changed: 0 ins; 0 del; 3 mod 8293154: TemporalQueries java doc error Reviewed-by: rriggs, lancea ------------- PR: https://git.openjdk.org/jdk/pull/10103 From ysatowse at openjdk.org Fri Sep 2 12:44:14 2022 From: ysatowse at openjdk.org (Yoshiki Sato) Date: Fri, 2 Sep 2022 12:44:14 GMT Subject: RFR: 8292579: (tz) Update Timezone Data to 2022c Message-ID: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Please review this PR. The PR adopts the official tzdata2022c as it is. It means the pre-1970s data merged in tzdata2022c doesn't exist. All tests have been passed with no failures. ------------- Commit messages: - Merge branch 'master' into tz2022c - The first fix for tz2022c Changes: https://git.openjdk.org/jdk/pull/10012/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10012&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8292579 Stats: 1021 lines in 15 files changed: 256 ins; 613 del; 152 mod Patch: https://git.openjdk.org/jdk/pull/10012.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10012/head:pull/10012 PR: https://git.openjdk.org/jdk/pull/10012 From ysatowse at openjdk.org Fri Sep 2 12:44:14 2022 From: ysatowse at openjdk.org (Yoshiki Sato) Date: Fri, 2 Sep 2022 12:44:14 GMT Subject: RFR: 8292579: (tz) Update Timezone Data to 2022c In-Reply-To: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> References: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Message-ID: On Thu, 25 Aug 2022 02:26:19 GMT, Yoshiki Sato wrote: > Please review this PR. The PR adopts the official tzdata2022c as it is. > It means the pre-1970s data merged in tzdata2022c doesn't exist. > All tests have been passed with no failures. The test failure seems to be irrelevant to this fix. Problem listed by [JDK-8292498](https://bugs.openjdk.org/browse/JDK-8292498) and also mentioned as that the failure may occur on non-Windows platforms. https://bugs.openjdk.org/browse/JDK-8292498?focusedCommentId=14518336&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14518336 ------------- PR: https://git.openjdk.org/jdk/pull/10012 From naoto at openjdk.org Fri Sep 2 16:24:43 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 2 Sep 2022 16:24:43 GMT Subject: RFR: 8292579: (tz) Update Timezone Data to 2022c In-Reply-To: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> References: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Message-ID: On Thu, 25 Aug 2022 02:26:19 GMT, Yoshiki Sato wrote: > Please review this PR. The PR adopts the official tzdata2022c as it is. > It means the pre-1970s data merged in tzdata2022c doesn't exist. > All tests have been passed with no failures. LGTM ------------- Marked as reviewed by naoto (Reviewer). PR: https://git.openjdk.org/jdk/pull/10012 From alanb at openjdk.org Sat Sep 3 07:27:42 2022 From: alanb at openjdk.org (Alan Bateman) Date: Sat, 3 Sep 2022 07:27:42 GMT Subject: RFR: 8292579: (tz) Update Timezone Data to 2022c In-Reply-To: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> References: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Message-ID: On Thu, 25 Aug 2022 02:26:19 GMT, Yoshiki Sato wrote: > Please review this PR. The PR adopts the official tzdata2022c as it is. > It means the pre-1970s data merged in tzdata2022c doesn't exist. > All tests have been passed with no failures. Marked as reviewed by alanb (Reviewer). ------------- PR: https://git.openjdk.org/jdk/pull/10012 From ihse at openjdk.org Tue Sep 6 12:29:23 2022 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Tue, 6 Sep 2022 12:29:23 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v7] In-Reply-To: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: > I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. > > I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. > > I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). > > The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. Magnus Ihse Bursie has updated the pull request incrementally with two additional commits since the last revision: - Revert changes in libjpeg - Revert changes in libfreetype ------------- Changes: - all: https://git.openjdk.org/jdk/pull/8328/files - new: https://git.openjdk.org/jdk/pull/8328/files/98e635a5..19409c23 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=8328&range=06 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=8328&range=05-06 Stats: 9 lines in 6 files changed: 0 ins; 0 del; 9 mod Patch: https://git.openjdk.org/jdk/pull/8328.diff Fetch: git fetch https://git.openjdk.org/jdk pull/8328/head:pull/8328 PR: https://git.openjdk.org/jdk/pull/8328 From ihse at openjdk.org Tue Sep 6 12:42:05 2022 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Tue, 6 Sep 2022 12:42:05 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v8] In-Reply-To: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: > I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. > > I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. > > I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). > > The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 46 commits: - Merge branch 'master' into typos-in-java.desktop - Revert changes in libjpeg - Revert changes in libfreetype - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - Update src/java.desktop/share/classes/sun/awt/image/ImagingLib.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - Update src/java.desktop/share/classes/sun/awt/image/ImagingLib.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - ... and 36 more: https://git.openjdk.org/jdk/compare/6a1e98cb...1ce28314 ------------- Changes: https://git.openjdk.org/jdk/pull/8328/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=8328&range=07 Stats: 1028 lines in 486 files changed: 0 ins; 0 del; 1028 mod Patch: https://git.openjdk.org/jdk/pull/8328.diff Fetch: git fetch https://git.openjdk.org/jdk pull/8328/head:pull/8328 PR: https://git.openjdk.org/jdk/pull/8328 From ihse at openjdk.org Tue Sep 6 12:42:05 2022 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Tue, 6 Sep 2022 12:42:05 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v7] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Tue, 6 Sep 2022 12:29:23 GMT, Magnus Ihse Bursie wrote: >> I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. >> >> I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. >> >> I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). >> >> The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. > > Magnus Ihse Bursie has updated the pull request incrementally with two additional commits since the last revision: > > - Revert changes in libjpeg > - Revert changes in libfreetype I have now removed the changes to libfreetype, and also libjpeg. These were the only 3rd party source I could locate. I apologize for this PR. It was too huge. If it is of any comfort, I've learnt my lesson and won't repeat it. And once it started getting pushed down by more prioritized work, I got a bit scared about going back and look through all this for additional (unspecified) 3rd party sources, so it got left behind, hanging around. @prrace I hope this is acceptable to merge now. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From ysatowse at openjdk.org Tue Sep 6 16:09:09 2022 From: ysatowse at openjdk.org (Yoshiki Sato) Date: Tue, 6 Sep 2022 16:09:09 GMT Subject: Integrated: 8292579: (tz) Update Timezone Data to 2022c In-Reply-To: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> References: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Message-ID: On Thu, 25 Aug 2022 02:26:19 GMT, Yoshiki Sato wrote: > Please review this PR. The PR adopts the official tzdata2022c as it is. > It means the pre-1970s data merged in tzdata2022c doesn't exist. > All tests have been passed with no failures. This pull request has now been integrated. Changeset: 98d85e6f Author: Yoshiki Sato Committer: Naoto Sato URL: https://git.openjdk.org/jdk/commit/98d85e6f594bf34b97407c470b14791af0a2bc53 Stats: 1021 lines in 15 files changed: 256 ins; 613 del; 152 mod 8292579: (tz) Update Timezone Data to 2022c Reviewed-by: naoto, alanb ------------- PR: https://git.openjdk.org/jdk/pull/10012 From naoto at openjdk.org Tue Sep 6 17:36:38 2022 From: naoto at openjdk.org (Naoto Sato) Date: Tue, 6 Sep 2022 17:36:38 GMT Subject: RFR: 8293146: Strict DateTimeFormatter fails to report an invalid week 53 Message-ID: Fixed the max week number on parsing the week of week-based year field in strict mode. It used to be always returning the largest maximum, which should be adjusted by the actual week-based year. ------------- Commit messages: - 8293146: Strict DateTimeFormatter fails to report an invalid week 53 Changes: https://git.openjdk.org/jdk/pull/10184/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10184&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8293146 Stats: 65 lines in 2 files changed: 61 ins; 0 del; 4 mod Patch: https://git.openjdk.org/jdk/pull/10184.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10184/head:pull/10184 PR: https://git.openjdk.org/jdk/pull/10184 From naoto at openjdk.org Tue Sep 6 19:06:45 2022 From: naoto at openjdk.org (Naoto Sato) Date: Tue, 6 Sep 2022 19:06:45 GMT Subject: RFR: 8293146: Strict DateTimeFormatter fails to report an invalid week 53 [v2] In-Reply-To: References: Message-ID: > Fixed the max week number on parsing the week of week-based year field in strict mode. It used to be always returning the largest maximum, which should be adjusted by the actual week-based year. Naoto Sato has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains three additional commits since the last revision: - Merge branch 'master' into JDK-8293146-StrictDateTimeFormatter - Fixed typo - 8293146: Strict DateTimeFormatter fails to report an invalid week 53 ------------- Changes: - all: https://git.openjdk.org/jdk/pull/10184/files - new: https://git.openjdk.org/jdk/pull/10184/files/7c7a532c..be54a7be Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=10184&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=10184&range=00-01 Stats: 27962 lines in 532 files changed: 10072 ins; 12327 del; 5563 mod Patch: https://git.openjdk.org/jdk/pull/10184.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10184/head:pull/10184 PR: https://git.openjdk.org/jdk/pull/10184 From rriggs at openjdk.org Wed Sep 7 17:46:43 2022 From: rriggs at openjdk.org (Roger Riggs) Date: Wed, 7 Sep 2022 17:46:43 GMT Subject: RFR: 8293146: Strict DateTimeFormatter fails to report an invalid week 53 [v2] In-Reply-To: References: Message-ID: On Tue, 6 Sep 2022 19:06:45 GMT, Naoto Sato wrote: >> Fixed the max week number on parsing the week of week-based year field in strict mode. It used to be always returning the largest maximum, which should be adjusted by the actual week-based year. > > Naoto Sato has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains three additional commits since the last revision: > > - Merge branch 'master' into JDK-8293146-StrictDateTimeFormatter > - Fixed typo > - 8293146: Strict DateTimeFormatter fails to report an invalid week 53 LGTM ------------- Marked as reviewed by rriggs (Reviewer). PR: https://git.openjdk.org/jdk/pull/10184 From naoto at openjdk.org Wed Sep 7 18:37:51 2022 From: naoto at openjdk.org (Naoto Sato) Date: Wed, 7 Sep 2022 18:37:51 GMT Subject: Integrated: 8293146: Strict DateTimeFormatter fails to report an invalid week 53 In-Reply-To: References: Message-ID: On Tue, 6 Sep 2022 17:30:27 GMT, Naoto Sato wrote: > Fixed the max week number on parsing the week of week-based year field in strict mode. It used to be always returning the largest maximum, which should be adjusted by the actual week-based year. This pull request has now been integrated. Changeset: 32c7b628 Author: Naoto Sato URL: https://git.openjdk.org/jdk/commit/32c7b6283daf6f3876ff62693d5a0cb7c4af4232 Stats: 65 lines in 2 files changed: 61 ins; 0 del; 4 mod 8293146: Strict DateTimeFormatter fails to report an invalid week 53 Reviewed-by: rriggs ------------- PR: https://git.openjdk.org/jdk/pull/10184 From smarks at openjdk.org Wed Sep 7 23:23:42 2022 From: smarks at openjdk.org (Stuart Marks) Date: Wed, 7 Sep 2022 23:23:42 GMT Subject: RFR: 8291660: Grapheme support in BreakIterator [v4] In-Reply-To: References: Message-ID: On Fri, 26 Aug 2022 21:48:14 GMT, Naoto Sato wrote: >> This is to enhance the character break analysis in `java.text.BreakIterator` to conform to the extended grapheme cluster boundaries defined in https://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries. A corresponding CSR has also been drafted, as there will be behavioral changes with this modification. > > Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: > > Changed the paragraph to @implSpec src/java.base/share/classes/jdk/internal/util/regex/Grapheme.java line 47: > 45: */ > 46: public static int nextBoundary(CharSequence src, int off, int limit) { > 47: Objects.checkFromToIndex(0, limit - off, src.length()); Is this right? The old code's use of `checkFromToIndex` method seems to be the right way to check that `off` and `limit` are a valid from-to range within `[0, src.length)`. The new code subtracts `off` from both args but the arithmetic seems to allow for some errors. For example, depending on the value of `limit`, this might permit `off` to be a small negative number. src/java.base/share/classes/sun/util/locale/provider/BreakIteratorProviderImpl.java line 135: > 133: public BreakIterator getCharacterInstance(Locale locale) { > 134: return new GraphemeBreakIterator(); > 135: } It looks like there is some kind of table Since CHARACTER_INDEX is no longer used, does it mean there is now dead code for the CHARACTER break iterator class, and dead resources for CharacterData and CharacterDictionary? Should this be removed? Or maybe this is all in each locale or something and should be cleaned up later? ------------- PR: https://git.openjdk.org/jdk/pull/9991 From naoto at openjdk.org Thu Sep 8 16:11:57 2022 From: naoto at openjdk.org (Naoto Sato) Date: Thu, 8 Sep 2022 16:11:57 GMT Subject: RFR: 8291660: Grapheme support in BreakIterator [v5] In-Reply-To: References: Message-ID: <1FaPRQjWWE3I3jAyr2vyRnecYFIve45caRkDzNRLr1g=.fa0237b6-2793-49a1-8349-ab09371bf151@github.com> > This is to enhance the character break analysis in `java.text.BreakIterator` to conform to the extended grapheme cluster boundaries defined in https://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries. A corresponding CSR has also been drafted, as there will be behavioral changes with this modification. Naoto Sato has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains ten additional commits since the last revision: - Reverted the index checking fix - Removed character break data which is no longer needed - Merge branch 'master' into JDK-8291660-graphemes - Changed the paragraph to @implSpec - Reverting the fix to BreakIterator.isBoundary() - Fixing JCK failures - Addressing review comments - 8291660: Grapheme support in BreakIterator - 8291660: Add a method to stream extended grapheme clusters in a String ------------- Changes: - all: https://git.openjdk.org/jdk/pull/9991/files - new: https://git.openjdk.org/jdk/pull/9991/files/06cfc222..2f31d417 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=9991&range=04 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=9991&range=03-04 Stats: 74365 lines in 1082 files changed: 32063 ins; 34006 del; 8296 mod Patch: https://git.openjdk.org/jdk/pull/9991.diff Fetch: git fetch https://git.openjdk.org/jdk pull/9991/head:pull/9991 PR: https://git.openjdk.org/jdk/pull/9991 From naoto at openjdk.org Thu Sep 8 16:14:30 2022 From: naoto at openjdk.org (Naoto Sato) Date: Thu, 8 Sep 2022 16:14:30 GMT Subject: RFR: 8291660: Grapheme support in BreakIterator [v4] In-Reply-To: References: Message-ID: <_ROpfVbWGm458N8rQ6gUOmfUArxrl7Ufm3slZUwjX5A=.06e59d20-50c8-4d03-a16f-4fdc7fdcd85c@github.com> On Wed, 7 Sep 2022 21:27:10 GMT, Stuart Marks wrote: >> Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: >> >> Changed the paragraph to @implSpec > > src/java.base/share/classes/jdk/internal/util/regex/Grapheme.java line 47: > >> 45: */ >> 46: public static int nextBoundary(CharSequence src, int off, int limit) { >> 47: Objects.checkFromToIndex(0, limit - off, src.length()); > > Is this right? The old code's use of `checkFromToIndex` method seems to be the right way to check that `off` and `limit` are a valid from-to range within `[0, src.length)`. The new code subtracts `off` from both args but the arithmetic seems to allow for some errors. For example, depending on the value of `limit`, this might permit `off` to be a small negative number. Thanks for the catch! Yes, this was a leftover before I fixed a couple of JCK failures which correctly fixed edge cases. Reverted the change. > src/java.base/share/classes/sun/util/locale/provider/BreakIteratorProviderImpl.java line 135: > >> 133: public BreakIterator getCharacterInstance(Locale locale) { >> 134: return new GraphemeBreakIterator(); >> 135: } > > It looks like there is some kind of table Since CHARACTER_INDEX is no longer used, does it mean there is now dead code for the CHARACTER break iterator class, and dead resources for CharacterData and CharacterDictionary? Should this be removed? Or maybe this is all in each locale or something and should be cleaned up later? Right. Removed the now-dead code. ------------- PR: https://git.openjdk.org/jdk/pull/9991 From naoto at openjdk.org Thu Sep 8 18:32:56 2022 From: naoto at openjdk.org (Naoto Sato) Date: Thu, 8 Sep 2022 18:32:56 GMT Subject: RFR: 8291660: Grapheme support in BreakIterator [v6] In-Reply-To: References: Message-ID: <-vMSsSpfdN9yInhc30W0R3MNURpC7WuLr0xehsufqxs=.479c0683-e3c3-47cb-b83e-e83108077094@github.com> > This is to enhance the character break analysis in `java.text.BreakIterator` to conform to the extended grapheme cluster boundaries defined in https://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries. A corresponding CSR has also been drafted, as there will be behavioral changes with this modification. Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: Removed unnecessary comments ------------- Changes: - all: https://git.openjdk.org/jdk/pull/9991/files - new: https://git.openjdk.org/jdk/pull/9991/files/2f31d417..e8e037c2 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=9991&range=05 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=9991&range=04-05 Stats: 2 lines in 1 file changed: 0 ins; 2 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/9991.diff Fetch: git fetch https://git.openjdk.org/jdk pull/9991/head:pull/9991 PR: https://git.openjdk.org/jdk/pull/9991 From itakiguchi at openjdk.org Fri Sep 9 06:29:44 2022 From: itakiguchi at openjdk.org (Ichiroh Takiguchi) Date: Fri, 9 Sep 2022 06:29:44 GMT Subject: RFR: 8291916: Unexpected output on Windows command prompt In-Reply-To: References: Message-ID: On Tue, 9 Aug 2022 20:38:25 GMT, Naoto Sato wrote: >> To support Windows command prompt's codepage, following charsets should be moved from jdk.charsets module to java.base module. >> >> - IBM860 >> - IBM861 >> - IBM863 >> - IBM864 >> - IBM865 >> - IBM869 > > I looked at this issue a bit more. It looks to me that the issue is caused by the fact that the encoding of `System.out` falls back to the default encoding, as `IBM864` is not in `java.base`. This issue seems not new and reproducible with the releases since JDK9 where modularization has been introduced. Also, I think other encodings than those `IBM*` listed here, can possibly cause this issue. In order to fix this completely, those obscure encodings also have to be in `java.base` which I don't think we would want to do. Hello @naotoj . Sorry for my bad reaction. I checked these charsets with IBM CDRA definitions. These are also same, but some round-trip definitions are not same, like #9661 . I think there come from files under https://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/PC/ . As you know, `CP860/CP861/CP863/CP864/CP865/CP869` are defined into [IANA Character Sets](https://www.iana.org/assignments/character-sets/character-sets.xhtml) as an alias. Even if the registered names are `IBM*`, these charset implementations are from Microsoft. I think these charset should be usable as default charset on Windows command prompt. Please reconsider current Java implementation. ------------- PR: https://git.openjdk.org/jdk/pull/9761 From smarks at openjdk.org Fri Sep 9 17:07:42 2022 From: smarks at openjdk.org (Stuart Marks) Date: Fri, 9 Sep 2022 17:07:42 GMT Subject: RFR: 8291660: Grapheme support in BreakIterator [v6] In-Reply-To: <-vMSsSpfdN9yInhc30W0R3MNURpC7WuLr0xehsufqxs=.479c0683-e3c3-47cb-b83e-e83108077094@github.com> References: <-vMSsSpfdN9yInhc30W0R3MNURpC7WuLr0xehsufqxs=.479c0683-e3c3-47cb-b83e-e83108077094@github.com> Message-ID: On Thu, 8 Sep 2022 18:32:56 GMT, Naoto Sato wrote: >> This is to enhance the character break analysis in `java.text.BreakIterator` to conform to the extended grapheme cluster boundaries defined in https://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries. A corresponding CSR has also been drafted, as there will be behavioral changes with this modification. > > Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: > > Removed unnecessary comments Updates look good, assuming all the tests pass. ------------- Marked as reviewed by smarks (Reviewer). PR: https://git.openjdk.org/jdk/pull/9991 From naoto at openjdk.org Fri Sep 9 17:17:49 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 9 Sep 2022 17:17:49 GMT Subject: Integrated: 8291660: Grapheme support in BreakIterator In-Reply-To: References: Message-ID: On Tue, 23 Aug 2022 22:44:13 GMT, Naoto Sato wrote: > This is to enhance the character break analysis in `java.text.BreakIterator` to conform to the extended grapheme cluster boundaries defined in https://www.unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries. A corresponding CSR has also been drafted, as there will be behavioral changes with this modification. This pull request has now been integrated. Changeset: b8598b02 Author: Naoto Sato URL: https://git.openjdk.org/jdk/commit/b8598b02979dff8a947a523a6d76768a1bfe594b Stats: 348 lines in 15 files changed: 199 ins; 103 del; 46 mod 8291660: Grapheme support in BreakIterator Reviewed-by: smarks ------------- PR: https://git.openjdk.org/jdk/pull/9991 From naoto at openjdk.org Fri Sep 9 22:30:41 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 9 Sep 2022 22:30:41 GMT Subject: RFR: 8291916: Unexpected output on Windows command prompt In-Reply-To: References: Message-ID: On Fri, 5 Aug 2022 02:15:21 GMT, Ichiroh Takiguchi wrote: > To support Windows command prompt's codepage, following charsets should be moved from jdk.charsets module to java.base module. > > - IBM860 > - IBM861 > - IBM863 > - IBM864 > - IBM865 > - IBM869 Considering those code page encodings are legacy ones (Microsoft now endorses UTF-8 (cp65001) as the default encoding), I still don't think moving those charsets into java.base module is a good idea. Keeping the base module small is more important IMO. ------------- PR: https://git.openjdk.org/jdk/pull/9761 From aivanov at openjdk.org Tue Sep 13 20:07:53 2022 From: aivanov at openjdk.org (Alexey Ivanov) Date: Tue, 13 Sep 2022 20:07:53 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v8] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Tue, 6 Sep 2022 12:42:05 GMT, Magnus Ihse Bursie wrote: >> I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. >> >> I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. >> >> I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). >> >> The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. > > Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 46 commits: > > - Merge branch 'master' into typos-in-java.desktop > - Revert changes in libjpeg > - Revert changes in libfreetype > - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/awt/image/ImagingLib.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/awt/image/ImagingLib.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - ... and 36 more: https://git.openjdk.org/jdk/compare/6a1e98cb...1ce28314 Is `src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c` a third-party code? src/java.desktop/macosx/native/libawt_lwawt/java2d/metal/MTLLayer.m line 87: > 85: J2dTraceLn4(J2D_TRACE_VERBOSE, > 86: "MTLLayer.blitTexture: uninitialized (mtlc=%p, javaLayer=%p, buffer=%p, device=%p)", self.ctx, > 87: self.javaLayer, self.buffer, ctx.device); Is this an intended change? Or does it come from a merge? May I suggest wrapping the line after the format string before `self.ctx`? It would make it easier to read. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From ihse at openjdk.org Tue Sep 13 21:26:53 2022 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Tue, 13 Sep 2022 21:26:53 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v8] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Tue, 13 Sep 2022 19:48:47 GMT, Alexey Ivanov wrote: >> Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 46 commits: >> >> - Merge branch 'master' into typos-in-java.desktop >> - Revert changes in libjpeg >> - Revert changes in libfreetype >> - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/share/classes/sun/awt/image/ImagingLib.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/share/classes/sun/awt/image/ImagingLib.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - ... and 36 more: https://git.openjdk.org/jdk/compare/6a1e98cb...1ce28314 > > src/java.desktop/macosx/native/libawt_lwawt/java2d/metal/MTLLayer.m line 87: > >> 85: J2dTraceLn4(J2D_TRACE_VERBOSE, >> 86: "MTLLayer.blitTexture: uninitialized (mtlc=%p, javaLayer=%p, buffer=%p, device=%p)", self.ctx, >> 87: self.javaLayer, self.buffer, ctx.device); > > Is this an intended change? Or does it come from a merge? > > May I suggest wrapping the line after the format string before `self.ctx`? It would make it easier to read. This is from the merge. The only difference wrt to current code is "devide" => "device". I can change wrapping if you request it, but I'd prefer to only fix typos. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From ihse at openjdk.org Tue Sep 13 21:30:43 2022 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Tue, 13 Sep 2022 21:30:43 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v8] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: <0dmtHVVEvfGWQ94u7xMbddzoHbESy3mV5Gh3vdDrh-A=.10ffa679-739f-457c-b77e-c8b26c36146d@github.com> On Tue, 13 Sep 2022 20:04:17 GMT, Alexey Ivanov wrote: > Is `src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c` a third-party code? I don't think so. I find no comments in the source code, or any kind of indication on this being so. If you say it is, I can revert the changes in that file. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From ihse at openjdk.org Tue Sep 13 21:36:10 2022 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Tue, 13 Sep 2022 21:36:10 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v8] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Tue, 6 Sep 2022 12:42:05 GMT, Magnus Ihse Bursie wrote: >> I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. >> >> I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. >> >> I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). >> >> The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. > > Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 46 commits: > > - Merge branch 'master' into typos-in-java.desktop > - Revert changes in libjpeg > - Revert changes in libfreetype > - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/awt/image/ImagingLib.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/awt/image/ImagingLib.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - ... and 36 more: https://git.openjdk.org/jdk/compare/6a1e98cb...1ce28314 I see now that Phil cryptically said: > Regarding changes in gif + freetype diff --git a/src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c b/src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c \ \ diff --git a/src/java.desktop/share/native/libfontmanager/freetypeScaler.c b/src/java.desktop/share/native/libfontmanager/freetypeScaler.c \ \ Please exclude ALL 3rd party libraries from this PR. That might be interpreted as stating that `gifdecoder.c` is 3rd party source code (although that was by no means clear to me the first time I read it). I'll revert the changes in that file, and also `src/java.desktop/share/native/libfontmanager/freetypeScaler.c`. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From prr at openjdk.org Tue Sep 13 22:05:46 2022 From: prr at openjdk.org (Phil Race) Date: Tue, 13 Sep 2022 22:05:46 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v8] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Tue, 13 Sep 2022 21:32:44 GMT, Magnus Ihse Bursie wrote: > I see now that Phil cryptically said: > > > Regarding changes in gif + freetype > > diff --git a/src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c b/src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c > > > > diff --git a/src/java.desktop/share/native/libfontmanager/freetypeScaler.c b/src/java.desktop/share/native/libfontmanager/freetypeScaler.c > > > > Please exclude ALL 3rd party libraries from this PR. > > That might be interpreted as stating that `gifdecoder.c` is 3rd party source code (although that was by no means clear to me the first time I read it). I'll revert the changes in that file, and also `src/java.desktop/share/native/libfontmanager/freetypeScaler.c`. I don't know why I mentioned those two files like that but those particular two are JDK code so are fair game. I did write "Please exclude ALL 3rd party libraries from this PR." and later : "We need to revert the native code changes to "libfreetype". and those points are correct. You did fix the latter, but there are still some 3rd party files in there that are edited : glext.h, wsutils.h, multiVis.c ------------- PR: https://git.openjdk.org/jdk/pull/8328 From andrew at openjdk.org Wed Sep 14 16:09:50 2022 From: andrew at openjdk.org (Andrew John Hughes) Date: Wed, 14 Sep 2022 16:09:50 GMT Subject: RFR: 8292579: (tz) Update Timezone Data to 2022c In-Reply-To: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> References: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Message-ID: On Thu, 25 Aug 2022 02:26:19 GMT, Yoshiki Sato wrote: > Please review this PR. The PR adopts the official tzdata2022c as it is. > It means the pre-1970s data merged in tzdata2022c doesn't exist. > All tests have been passed with no failures. Should this not have included an update to the resource bundles - as with https://github.com/openjdk/jdk/commit/ad3be04d2ac84836e393d696ff03ddfe72779094 - so that `Europe/Kyiv` is recognised? ------------- PR: https://git.openjdk.org/jdk/pull/10012 From andrew at openjdk.org Wed Sep 14 16:14:47 2022 From: andrew at openjdk.org (Andrew John Hughes) Date: Wed, 14 Sep 2022 16:14:47 GMT Subject: RFR: 8292579: (tz) Update Timezone Data to 2022c In-Reply-To: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> References: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Message-ID: On Thu, 25 Aug 2022 02:26:19 GMT, Yoshiki Sato wrote: > Please review this PR. The PR adopts the official tzdata2022c as it is. > It means the pre-1970s data merged in tzdata2022c doesn't exist. > All tests have been passed with no failures. That is something we've patched locally e.g. https://src.fedoraproject.org/rpms/java-11-openjdk/pull-request/163 and we have a test which fails without and passes with, though it does use `sun.util.resources` directly. ------------- PR: https://git.openjdk.org/jdk/pull/10012 From naoto at openjdk.org Wed Sep 14 19:30:48 2022 From: naoto at openjdk.org (Naoto Sato) Date: Wed, 14 Sep 2022 19:30:48 GMT Subject: RFR: 8292579: (tz) Update Timezone Data to 2022c In-Reply-To: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> References: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Message-ID: On Thu, 25 Aug 2022 02:26:19 GMT, Yoshiki Sato wrote: > Please review this PR. The PR adopts the official tzdata2022c as it is. > It means the pre-1970s data merged in tzdata2022c doesn't exist. > All tests have been passed with no failures. Names are retrieved through aliases, so I think there is no need to add extra names in the COMPAT resource bundles. % ./build/macosx-aarch64/jdk/bin/jshell -R-Djava.locale.providers=COMPAT JAVASE | Welcome to JShell -- Version 20-internal | For an introduction type: /help intro jshell> ZoneId.of("Europe/Kyiv").getDisplayName(TextStyle.FULL, Locale.US) $178 ==> "Eastern European Time" jshell> ZoneId.of("Europe/Kiev").getDisplayName(TextStyle.FULL, Locale.US) $179 ==> "Eastern European Time" jshell> ZoneId.of("Europe/Kyiv").getDisplayName(TextStyle.FULL, Locale.JAPAN) $180 ==> "?????????" jshell> ZoneId.of("Europe/Kiev").getDisplayName(TextStyle.FULL, Locale.JAPAN) $181 ==> "?????????" CLDR incorporated the Kyiv/Kiev aliasing in their upcoming version 42, JDK does not have the alias yet, thus: % ./build/macosx-aarch64/jdk/bin/jshell JAVASE | Welcome to JShell -- Version 20-internal | For an introduction type: /help intro jshell> ZoneId.of("Europe/Kyiv").getDisplayName(TextStyle.FULL, Locale.US) $178 ==> "Kyiv Time" jshell> ZoneId.of("Europe/Kiev").getDisplayName(TextStyle.FULL, Locale.US) $179 ==> "Eastern European Time" jshell> ZoneId.of("Europe/Kyiv").getDisplayName(TextStyle.FULL, Locale.JAPAN) $180 ==> "Kyiv??" jshell> ZoneId.of("Europe/Kiev").getDisplayName(TextStyle.FULL, Locale.JAPAN) $181 ==> "????????" jshell> ZoneId.of("Europe/Kiev").getDisplayName(TextStyle.FULL, Locale.JAPAN) This will be fixed once we incorporate CLDR v42 into JDK repository. Since we don't backport CLDR, TZ backports should separately cherry-pick the changes in timezone.xml, such as: diff --git a/make/data/cldr/common/bcp47/timezone.xml b/make/data/cldr/common/bcp47/timezone.xml index f0812776d5d..ddbccff077c 100644 --- a/make/data/cldr/common/bcp47/timezone.xml +++ b/make/data/cldr/common/bcp47/timezone.xml @@ -394,7 +394,7 @@ For terms of use, see http://www.unicode.org/copyright.html - + ------------- PR: https://git.openjdk.org/jdk/pull/10012 From aivanov at openjdk.org Wed Sep 14 20:08:47 2022 From: aivanov at openjdk.org (Alexey Ivanov) Date: Wed, 14 Sep 2022 20:08:47 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v8] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Tue, 13 Sep 2022 21:23:00 GMT, Magnus Ihse Bursie wrote: > I'd prefer to only fix typos. Let us keep only the typos. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From andrew at openjdk.org Thu Sep 15 02:01:52 2022 From: andrew at openjdk.org (Andrew John Hughes) Date: Thu, 15 Sep 2022 02:01:52 GMT Subject: RFR: 8292579: (tz) Update Timezone Data to 2022c In-Reply-To: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> References: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Message-ID: On Thu, 25 Aug 2022 02:26:19 GMT, Yoshiki Sato wrote: > Please review this PR. The PR adopts the official tzdata2022c as it is. > It means the pre-1970s data merged in tzdata2022c doesn't exist. > All tests have been passed with no failures. Interesting, I remember changes like this causing failures in the past. Maybe they were introducing completely new zones. It looks good for the old `java.util` API as well: ~~~ $ ~/builder/trunk/images/jdk/bin/jshell -R-Djava.locale.providers=COMPAT JAVASE | Welcome to JShell -- Version 20-internal | For an introduction type: /help intro jshell> ZoneId.of("Europe/Kyiv").getDisplayName(TextStyle.FULL, Locale.US) $178 ==> "Eastern European Time" jshell> TimeZone.getTimeZone("Europe/Kyiv").getDisplayName(false, TimeZone.LONG, Locale.US) $179 ==> "Eastern European Time" ~~~ and similar for 11u & 17u with an updated tzdb. I guess we just need the CLDR change in a backport then. ------------- PR: https://git.openjdk.org/jdk/pull/10012 From andrew at openjdk.org Thu Sep 15 02:22:50 2022 From: andrew at openjdk.org (Andrew John Hughes) Date: Thu, 15 Sep 2022 02:22:50 GMT Subject: RFR: 8292579: (tz) Update Timezone Data to 2022c In-Reply-To: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> References: <-TnMh7j1g6YYNA-EIE11kVkTxwPRSHlVHGJUXvrG8SM=.1c2263a9-b90c-478e-bcab-63a40f4d6ac4@github.com> Message-ID: On Thu, 25 Aug 2022 02:26:19 GMT, Yoshiki Sato wrote: > Please review this PR. The PR adopts the official tzdata2022c as it is. > It means the pre-1970s data merged in tzdata2022c doesn't exist. > All tests have been passed with no failures. I've opened https://bugs.openjdk.org/browse/JDK-8293834 for the CLDR backport and will open a PR tomorrow for 19u. ------------- PR: https://git.openjdk.org/jdk/pull/10012 From naoto at openjdk.org Mon Sep 19 19:20:18 2022 From: naoto at openjdk.org (Naoto Sato) Date: Mon, 19 Sep 2022 19:20:18 GMT Subject: RFR: 8294008: Graphme implementation of setText() throws IndexOutOfBoundsException Message-ID: Fixing JCK failures caused by the new grapheme implementation. The length of a CharSequence should return the `endIndex`, not `endIndex - beginIndex`. ------------- Commit messages: - 8294008: Graphme implementation of setText() throws IndexOutOfBoundsException Changes: https://git.openjdk.org/jdk/pull/10349/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10349&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8294008 Stats: 6 lines in 2 files changed: 5 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/10349.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10349/head:pull/10349 PR: https://git.openjdk.org/jdk/pull/10349 From joehw at openjdk.org Mon Sep 19 20:49:48 2022 From: joehw at openjdk.org (Joe Wang) Date: Mon, 19 Sep 2022 20:49:48 GMT Subject: RFR: 8294008: Graphme implementation of setText() throws IndexOutOfBoundsException In-Reply-To: References: Message-ID: <9q1PEg15HYOhUIrTfUdKhpbUcXjpppP6JANXsj6Mlsw=.b5a81583-9470-4b68-b824-7a11583a8b70@github.com> On Mon, 19 Sep 2022 19:01:57 GMT, Naoto Sato wrote: > Fixing JCK failures caused by the new grapheme implementation. The length of a CharSequence should return the `endIndex`, not `endIndex - beginIndex`. src/java.base/share/classes/sun/util/locale/provider/BreakIteratorProviderImpl.java line 329: > 327: @Override > 328: public int length() { > 329: return src.getEndIndex(); Could the issue be somewhere else? I mean it feels correct for length = endIndex - beginIndex. ------------- PR: https://git.openjdk.org/jdk/pull/10349 From naoto at openjdk.org Mon Sep 19 21:04:52 2022 From: naoto at openjdk.org (Naoto Sato) Date: Mon, 19 Sep 2022 21:04:52 GMT Subject: RFR: 8294008: Graphme implementation of setText() throws IndexOutOfBoundsException In-Reply-To: <9q1PEg15HYOhUIrTfUdKhpbUcXjpppP6JANXsj6Mlsw=.b5a81583-9470-4b68-b824-7a11583a8b70@github.com> References: <9q1PEg15HYOhUIrTfUdKhpbUcXjpppP6JANXsj6Mlsw=.b5a81583-9470-4b68-b824-7a11583a8b70@github.com> Message-ID: <8o6GmYySek8iJI4rvXiSMxKhjI8UZyRORQeCVwaidzM=.ae213824-aca7-4162-a0c0-9cd39682160a@github.com> On Mon, 19 Sep 2022 20:46:08 GMT, Joe Wang wrote: >> Fixing JCK failures caused by the new grapheme implementation. The length of a CharSequence should return the `endIndex`, not `endIndex - beginIndex`. > > src/java.base/share/classes/sun/util/locale/provider/BreakIteratorProviderImpl.java line 329: > >> 327: @Override >> 328: public int length() { >> 329: return src.getEndIndex(); > > Could the issue be somewhere else? I mean it feels correct for length = endIndex - beginIndex. It's somewhat confusing as this class adapts `CharacterIterator` into `CharSequence` which are similar to each other (thus the bug). Those `beginIndex`/`endIndex` designate the range in the source `CharacterIterator`, and this `length()` method should return the entire text length of the `CharSequence` nevertheless, thus it should start from `0` to `endIndex`. ------------- PR: https://git.openjdk.org/jdk/pull/10349 From joehw at openjdk.org Mon Sep 19 22:10:16 2022 From: joehw at openjdk.org (Joe Wang) Date: Mon, 19 Sep 2022 22:10:16 GMT Subject: RFR: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException In-Reply-To: References: Message-ID: On Mon, 19 Sep 2022 19:01:57 GMT, Naoto Sato wrote: > Fixing JCK failures caused by the new grapheme implementation. The length of a CharSequence should return the `endIndex`, not `endIndex - beginIndex`. Marked as reviewed by joehw (Reviewer). ------------- PR: https://git.openjdk.org/jdk/pull/10349 From joehw at openjdk.org Mon Sep 19 22:10:17 2022 From: joehw at openjdk.org (Joe Wang) Date: Mon, 19 Sep 2022 22:10:17 GMT Subject: RFR: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException In-Reply-To: <8o6GmYySek8iJI4rvXiSMxKhjI8UZyRORQeCVwaidzM=.ae213824-aca7-4162-a0c0-9cd39682160a@github.com> References: <9q1PEg15HYOhUIrTfUdKhpbUcXjpppP6JANXsj6Mlsw=.b5a81583-9470-4b68-b824-7a11583a8b70@github.com> <8o6GmYySek8iJI4rvXiSMxKhjI8UZyRORQeCVwaidzM=.ae213824-aca7-4162-a0c0-9cd39682160a@github.com> Message-ID: <9Zrf4UTRoFOdKg2lMZjHngzPuPnpiR3TgNtgpg_P1Go=.258d28fe-e571-40b9-b5b1-5154d09df9eb@github.com> On Mon, 19 Sep 2022 21:02:38 GMT, Naoto Sato wrote: >> src/java.base/share/classes/sun/util/locale/provider/BreakIteratorProviderImpl.java line 329: >> >>> 327: @Override >>> 328: public int length() { >>> 329: return src.getEndIndex(); >> >> Could the issue be somewhere else? I mean it feels correct for length = endIndex - beginIndex. > > It's somewhat confusing as this class adapts `CharacterIterator` into `CharSequence` which are similar to each other (thus the bug). Those `beginIndex`/`endIndex` designate the range in the source `CharacterIterator`, and this `length()` method should return the entire text length of the `CharSequence` nevertheless, thus it should start from `0` to `endIndex`. Yeah, I saw there's a mismatch between the src and limit in this call that led to the index check Exception: 286 for (int b = ci.getBeginIndex(); b < end;) { 287 boundaries.add(b); 288 b = Grapheme.nextBoundary(text, b, end); 289 } and nextBoundary could walk through the entire CharSequence. Maybe it's worth a note to the length() method. ------------- PR: https://git.openjdk.org/jdk/pull/10349 From naoto at openjdk.org Mon Sep 19 22:21:44 2022 From: naoto at openjdk.org (Naoto Sato) Date: Mon, 19 Sep 2022 22:21:44 GMT Subject: RFR: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException [v2] In-Reply-To: References: Message-ID: > Fixing JCK failures caused by the new grapheme implementation. The length of a CharSequence should return the `endIndex`, not `endIndex - beginIndex`. Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: Added comments to length() ------------- Changes: - all: https://git.openjdk.org/jdk/pull/10349/files - new: https://git.openjdk.org/jdk/pull/10349/files/2b176cd6..85291040 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=10349&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=10349&range=00-01 Stats: 3 lines in 1 file changed: 3 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/10349.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10349/head:pull/10349 PR: https://git.openjdk.org/jdk/pull/10349 From naoto at openjdk.org Mon Sep 19 22:21:45 2022 From: naoto at openjdk.org (Naoto Sato) Date: Mon, 19 Sep 2022 22:21:45 GMT Subject: RFR: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException [v2] In-Reply-To: <9Zrf4UTRoFOdKg2lMZjHngzPuPnpiR3TgNtgpg_P1Go=.258d28fe-e571-40b9-b5b1-5154d09df9eb@github.com> References: <9q1PEg15HYOhUIrTfUdKhpbUcXjpppP6JANXsj6Mlsw=.b5a81583-9470-4b68-b824-7a11583a8b70@github.com> <8o6GmYySek8iJI4rvXiSMxKhjI8UZyRORQeCVwaidzM=.ae213824-aca7-4162-a0c0-9cd39682160a@github.com> <9Zrf4UTRoFOdKg2lMZjHngzPuPnpiR3TgNtgpg_P1Go=.258d28fe-e571-40b9-b5b1-5154d09df9eb@github.com> Message-ID: On Mon, 19 Sep 2022 22:07:13 GMT, Joe Wang wrote: >> It's somewhat confusing as this class adapts `CharacterIterator` into `CharSequence` which are similar to each other (thus the bug). Those `beginIndex`/`endIndex` designate the range in the source `CharacterIterator`, and this `length()` method should return the entire text length of the `CharSequence` nevertheless, thus it should start from `0` to `endIndex`. > > Yeah, I saw there's a mismatch between the src and limit in this call that led to the index check Exception: > 286 for (int b = ci.getBeginIndex(); b < end;) { > 287 boundaries.add(b); > 288 b = Grapheme.nextBoundary(text, b, end); > 289 } > > and nextBoundary could walk through the entire CharSequence. Maybe it's worth a note to the length() method. Thanks, Joe. Added comment to the method. ------------- PR: https://git.openjdk.org/jdk/pull/10349 From smarks at openjdk.org Mon Sep 19 23:07:43 2022 From: smarks at openjdk.org (Stuart Marks) Date: Mon, 19 Sep 2022 23:07:43 GMT Subject: RFR: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException [v2] In-Reply-To: References: <9q1PEg15HYOhUIrTfUdKhpbUcXjpppP6JANXsj6Mlsw=.b5a81583-9470-4b68-b824-7a11583a8b70@github.com> <8o6GmYySek8iJI4rvXiSMxKhjI8UZyRORQeCVwaidzM=.ae213824-aca7-4162-a0c0-9cd39682160a@github.com> <9Zrf4UTRoFOdKg2lMZjHngzPuPnpiR3TgNtgpg_P1Go=.258d28fe-e571-40b9-b5b1-5154d09df9eb@github.com> Message-ID: On Mon, 19 Sep 2022 22:18:42 GMT, Naoto Sato wrote: >> Yeah, I saw there's a mismatch between the src and limit in this call that led to the index check Exception: >> 286 for (int b = ci.getBeginIndex(); b < end;) { >> 287 boundaries.add(b); >> 288 b = Grapheme.nextBoundary(text, b, end); >> 289 } >> >> and nextBoundary could walk through the entire CharSequence. Maybe it's worth a note to the length() method. > > Thanks, Joe. Added comment to the method. OK yeah this is really confusing. One might ask a similar question in `charAt` about why it doesn't call src.setIndex(index + src.getBeginIndex()); The answer is that this is a special-purpose `CharSequence` that represents characters in the index range [0..endIndex) of the underlying `CharacterIterator`, **even if** that `CharacterIterator` represents the subrange of some string. As Joe noted, the calling code in `GraphemeBreakIterator` takes care to ensure that only valid indexes into the `src` are used. I think the comment on `length` helps a little bit but maybe a class-level comment would be better, since it applies to the whole model of this special `CharSequence` and not just the `length` method. Just a sentence or two is sufficient. Feel free to crib from the above. ------------- PR: https://git.openjdk.org/jdk/pull/10349 From naoto at openjdk.org Tue Sep 20 01:14:38 2022 From: naoto at openjdk.org (Naoto Sato) Date: Tue, 20 Sep 2022 01:14:38 GMT Subject: RFR: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException [v3] In-Reply-To: References: Message-ID: > Fixing JCK failures caused by the new grapheme implementation. The length of a CharSequence should return the `endIndex`, not `endIndex - beginIndex`. Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: Refine the comments by adding class level description in CharacterIteratorCharSequence ------------- Changes: - all: https://git.openjdk.org/jdk/pull/10349/files - new: https://git.openjdk.org/jdk/pull/10349/files/85291040..f0a65ed0 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=10349&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=10349&range=01-02 Stats: 10 lines in 1 file changed: 8 ins; 0 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/10349.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10349/head:pull/10349 PR: https://git.openjdk.org/jdk/pull/10349 From naoto at openjdk.org Tue Sep 20 01:14:39 2022 From: naoto at openjdk.org (Naoto Sato) Date: Tue, 20 Sep 2022 01:14:39 GMT Subject: RFR: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException [v3] In-Reply-To: References: <9q1PEg15HYOhUIrTfUdKhpbUcXjpppP6JANXsj6Mlsw=.b5a81583-9470-4b68-b824-7a11583a8b70@github.com> <8o6GmYySek8iJI4rvXiSMxKhjI8UZyRORQeCVwaidzM=.ae213824-aca7-4162-a0c0-9cd39682160a@github.com> <9Zrf4UTRoFOdKg2lMZjHngzPuPnpiR3TgNtgpg_P1Go=.258d28fe-e571-40b9-b5b1-5154d09df9eb@github.com> Message-ID: On Mon, 19 Sep 2022 23:04:12 GMT, Stuart Marks wrote: >> Thanks, Joe. Added comment to the method. > > OK yeah this is really confusing. One might ask a similar question in `charAt` about why it doesn't call > > src.setIndex(index + src.getBeginIndex()); > > The answer is that this is a special-purpose `CharSequence` that represents characters in the index range [0..endIndex) of the underlying `CharacterIterator`, **even if** that `CharacterIterator` represents the subrange of some string. As Joe noted, the calling code in `GraphemeBreakIterator` takes care to ensure that only valid indexes into the `src` are used. > > I think the comment on `length` helps a little bit but maybe a class-level comment would be better, since it applies to the whole model of this special `CharSequence` and not just the `length` method. Just a sentence or two is sufficient. Feel free to crib from the above. Thanks, Stuart. I used the paragraph almost intact for the class description ? ------------- PR: https://git.openjdk.org/jdk/pull/10349 From smarks at openjdk.org Tue Sep 20 15:56:02 2022 From: smarks at openjdk.org (Stuart Marks) Date: Tue, 20 Sep 2022 15:56:02 GMT Subject: RFR: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException [v3] In-Reply-To: References: Message-ID: On Tue, 20 Sep 2022 01:14:38 GMT, Naoto Sato wrote: >> Fixing JCK failures caused by the new grapheme implementation. The length of a CharSequence should return the `endIndex`, not `endIndex - beginIndex`. > > Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: > > Refine the comments by adding class level description in CharacterIteratorCharSequence Marked as reviewed by smarks (Reviewer). ------------- PR: https://git.openjdk.org/jdk/pull/10349 From smarks at openjdk.org Tue Sep 20 15:56:02 2022 From: smarks at openjdk.org (Stuart Marks) Date: Tue, 20 Sep 2022 15:56:02 GMT Subject: RFR: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException [v3] In-Reply-To: References: <9q1PEg15HYOhUIrTfUdKhpbUcXjpppP6JANXsj6Mlsw=.b5a81583-9470-4b68-b824-7a11583a8b70@github.com> <8o6GmYySek8iJI4rvXiSMxKhjI8UZyRORQeCVwaidzM=.ae213824-aca7-4162-a0c0-9cd39682160a@github.com> <9Zrf4UTRoFOdKg2lMZjHngzPuPnpiR3TgNtgpg_P1Go=.258d28fe-e571-40b9-b5b1-5154d09df9eb@github.com> Message-ID: On Tue, 20 Sep 2022 01:09:29 GMT, Naoto Sato wrote: >> OK yeah this is really confusing. One might ask a similar question in `charAt` about why it doesn't call >> >> src.setIndex(index + src.getBeginIndex()); >> >> The answer is that this is a special-purpose `CharSequence` that represents characters in the index range [0..endIndex) of the underlying `CharacterIterator`, **even if** that `CharacterIterator` represents the subrange of some string. As Joe noted, the calling code in `GraphemeBreakIterator` takes care to ensure that only valid indexes into the `src` are used. >> >> I think the comment on `length` helps a little bit but maybe a class-level comment would be better, since it applies to the whole model of this special `CharSequence` and not just the `length` method. Just a sentence or two is sufficient. Feel free to crib from the above. > > Thanks, Stuart. I used the paragraph almost intact for the class description ? OK looks good. ------------- PR: https://git.openjdk.org/jdk/pull/10349 From naoto at openjdk.org Tue Sep 20 16:49:54 2022 From: naoto at openjdk.org (Naoto Sato) Date: Tue, 20 Sep 2022 16:49:54 GMT Subject: Integrated: 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException In-Reply-To: References: Message-ID: On Mon, 19 Sep 2022 19:01:57 GMT, Naoto Sato wrote: > Fixing JCK failures caused by the new grapheme implementation. The length of a CharSequence should return the `endIndex`, not `endIndex - beginIndex`. This pull request has now been integrated. Changeset: e3358e77 Author: Naoto Sato URL: https://git.openjdk.org/jdk/commit/e3358e77f524f4d448c2ebb7c5afd0aa432f0d44 Stats: 18 lines in 2 files changed: 16 ins; 0 del; 2 mod 8294008: Grapheme implementation of setText() throws IndexOutOfBoundsException Reviewed-by: joehw, smarks ------------- PR: https://git.openjdk.org/jdk/pull/10349 From ihse at openjdk.org Wed Sep 21 11:49:11 2022 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Wed, 21 Sep 2022 11:49:11 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v9] In-Reply-To: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: > I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. > > I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. > > I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). > > The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. Magnus Ihse Bursie has updated the pull request incrementally with two additional commits since the last revision: - Revert changes to glext.h - Revert changes to multiVis.c and wsutils.h ------------- Changes: - all: https://git.openjdk.org/jdk/pull/8328/files - new: https://git.openjdk.org/jdk/pull/8328/files/1ce28314..e9f67a30 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=8328&range=08 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=8328&range=07-08 Stats: 10 lines in 3 files changed: 0 ins; 0 del; 10 mod Patch: https://git.openjdk.org/jdk/pull/8328.diff Fetch: git fetch https://git.openjdk.org/jdk pull/8328/head:pull/8328 PR: https://git.openjdk.org/jdk/pull/8328 From ihse at openjdk.org Wed Sep 21 11:52:57 2022 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Wed, 21 Sep 2022 11:52:57 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: > I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. > > I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. > > I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). > > The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 49 commits: - Merge branch 'master' into typos-in-java.desktop - Revert changes to glext.h - Revert changes to multiVis.c and wsutils.h - Merge branch 'master' into typos-in-java.desktop - Revert changes in libjpeg - Revert changes in libfreetype - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> - ... and 39 more: https://git.openjdk.org/jdk/compare/cddd6def...2850610d ------------- Changes: https://git.openjdk.org/jdk/pull/8328/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=8328&range=09 Stats: 1018 lines in 483 files changed: 0 ins; 0 del; 1018 mod Patch: https://git.openjdk.org/jdk/pull/8328.diff Fetch: git fetch https://git.openjdk.org/jdk pull/8328/head:pull/8328 PR: https://git.openjdk.org/jdk/pull/8328 From ihse at openjdk.org Wed Sep 21 11:52:57 2022 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Wed, 21 Sep 2022 11:52:57 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v8] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: <9vrVAfhskr81N1Y120kxvtI9Y9y_Y5G50uDkW1Ynvh0=.569c74fd-5ae2-46f5-8bea-7e903e53ffc9@github.com> On Tue, 13 Sep 2022 22:03:44 GMT, Phil Race wrote: >> I see now that Phil cryptically said: >> >>> Regarding changes in gif + freetype >> diff --git a/src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c b/src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c \ >> \ >> diff --git a/src/java.desktop/share/native/libfontmanager/freetypeScaler.c b/src/java.desktop/share/native/libfontmanager/freetypeScaler.c \ >> \ >> Please exclude ALL 3rd party libraries from this PR. >> >> That might be interpreted as stating that `gifdecoder.c` is 3rd party source code (although that was by no means clear to me the first time I read it). I'll revert the changes in that file, and also `src/java.desktop/share/native/libfontmanager/freetypeScaler.c`. > >> I see now that Phil cryptically said: >> >> > Regarding changes in gif + freetype >> > diff --git a/src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c b/src/java.desktop/share/native/libawt/awt/image/gif/gifdecoder.c >> > >> > diff --git a/src/java.desktop/share/native/libfontmanager/freetypeScaler.c b/src/java.desktop/share/native/libfontmanager/freetypeScaler.c >> > >> > Please exclude ALL 3rd party libraries from this PR. >> >> That might be interpreted as stating that `gifdecoder.c` is 3rd party source code (although that was by no means clear to me the first time I read it). I'll revert the changes in that file, and also `src/java.desktop/share/native/libfontmanager/freetypeScaler.c`. > > I don't know why I mentioned those two files like that but those particular two are JDK code so are fair game. > > I did write > "Please exclude ALL 3rd party libraries from this PR." > and later : > "We need to revert the native code changes to "libfreetype". > and those points are correct. > > You did fix the latter, but there are still some 3rd party files in there that are edited : glext.h, wsutils.h, multiVis.c @prrace I have now reverted the changes to glext.h, wsutils.h and multiVis.c. Is this finally ready for merging? (Going forward, I think we absolutely need to have some way to document in the code tree that certain files is 3rd party, like the UPSTREAM notation I previously suggested, or some variant thereof. This "tribal knowledge" about what is 3rd party is not beneficial to anyone, and only wastes both your and my time...) ------------- PR: https://git.openjdk.org/jdk/pull/8328 From duke at openjdk.org Thu Sep 22 01:31:33 2022 From: duke at openjdk.org (SWinxy) Date: Thu, 22 Sep 2022 01:31:33 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Wed, 21 Sep 2022 11:52:57 GMT, Magnus Ihse Bursie wrote: >> I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. >> >> I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. >> >> I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). >> >> The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. > > Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 49 commits: > > - Merge branch 'master' into typos-in-java.desktop > - Revert changes to glext.h > - Revert changes to multiVis.c and wsutils.h > - Merge branch 'master' into typos-in-java.desktop > - Revert changes in libjpeg > - Revert changes in libfreetype > - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - ... and 39 more: https://git.openjdk.org/jdk/compare/cddd6def...2850610d src/java.desktop/share/classes/javax/swing/plaf/metal/MetalTheme.java line 68: > 66: public abstract class MetalTheme { > 67: > 68: // Constants identifying the various Fonts that a Theme can support I think this is possibly meant to say "constants that *our* theme can support"? ------------- PR: https://git.openjdk.org/jdk/pull/8328 From duke at openjdk.org Thu Sep 22 01:39:24 2022 From: duke at openjdk.org (SWinxy) Date: Thu, 22 Sep 2022 01:39:24 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Wed, 21 Sep 2022 11:52:57 GMT, Magnus Ihse Bursie wrote: >> I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. >> >> I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. >> >> I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). >> >> The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. > > Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 49 commits: > > - Merge branch 'master' into typos-in-java.desktop > - Revert changes to glext.h > - Revert changes to multiVis.c and wsutils.h > - Merge branch 'master' into typos-in-java.desktop > - Revert changes in libjpeg > - Revert changes in libfreetype > - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - ... and 39 more: https://git.openjdk.org/jdk/compare/cddd6def...2850610d src/java.desktop/share/classes/sun/awt/SunToolkit.java line 1434: > 1432: > 1433: /** > 1434: * Parameterless version of realsync which uses default timeout (see DEFAULT_WAIT_TIME). Suggestion: * Parameterless version of realsync which uses the {@link #DEFAULT_WAIT_TIME default timeout}. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From duke at openjdk.org Thu Sep 22 01:56:31 2022 From: duke at openjdk.org (SWinxy) Date: Thu, 22 Sep 2022 01:56:31 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Wed, 21 Sep 2022 11:52:57 GMT, Magnus Ihse Bursie wrote: >> I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. >> >> I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. >> >> I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). >> >> The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. > > Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 49 commits: > > - Merge branch 'master' into typos-in-java.desktop > - Revert changes to glext.h > - Revert changes to multiVis.c and wsutils.h > - Merge branch 'master' into typos-in-java.desktop > - Revert changes in libjpeg > - Revert changes in libfreetype > - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - ... and 39 more: https://git.openjdk.org/jdk/compare/cddd6def...2850610d Everything looks fine, and you can freely ignore my suggestions. They are just thoughts. And yeah we should probably earmark third party files to avoid "tribal knowledge". ------------- PR: https://git.openjdk.org/jdk/pull/8328 From aivanov at openjdk.org Thu Sep 22 16:58:39 2022 From: aivanov at openjdk.org (Alexey Ivanov) Date: Thu, 22 Sep 2022 16:58:39 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Thu, 22 Sep 2022 01:29:24 GMT, SWinxy wrote: >> Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 49 commits: >> >> - Merge branch 'master' into typos-in-java.desktop >> - Revert changes to glext.h >> - Revert changes to multiVis.c and wsutils.h >> - Merge branch 'master' into typos-in-java.desktop >> - Revert changes in libjpeg >> - Revert changes in libfreetype >> - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - ... and 39 more: https://git.openjdk.org/jdk/compare/cddd6def...2850610d > > src/java.desktop/share/classes/javax/swing/plaf/metal/MetalTheme.java line 68: > >> 66: public abstract class MetalTheme { >> 67: >> 68: // Constants identifying the various Fonts that a Theme can support > > I think this is possibly meant to say "constants that *our* theme can support"? Please submit a new JBS issue for it if you can; if you can't, I can submit one on your behalf. Possibly it meant to say ?_the_ theme?. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From aivanov at openjdk.org Thu Sep 22 17:03:27 2022 From: aivanov at openjdk.org (Alexey Ivanov) Date: Thu, 22 Sep 2022 17:03:27 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Thu, 22 Sep 2022 01:35:49 GMT, SWinxy wrote: >> Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 49 commits: >> >> - Merge branch 'master' into typos-in-java.desktop >> - Revert changes to glext.h >> - Revert changes to multiVis.c and wsutils.h >> - Merge branch 'master' into typos-in-java.desktop >> - Revert changes in libjpeg >> - Revert changes in libfreetype >> - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java >> >> Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> >> - ... and 39 more: https://git.openjdk.org/jdk/compare/cddd6def...2850610d > > src/java.desktop/share/classes/sun/awt/SunToolkit.java line 1434: > >> 1432: >> 1433: /** >> 1434: * Parameterless version of realsync which uses default timeout (see DEFAULT_WAIT_TIME). > > Suggestion: > > * Parameterless version of realsync which uses the {@link #DEFAULT_WAIT_TIME default timeout}. > > I mean this suggestion [might not be warranted](https://github.com/openjdk/jdk/pull/8328/files#r872596373). I'm for a clearer message: Parameterless version of `{@code realsSync}` which uses _the_ default timeout of `{@link #DEFAULT_WAIT_TIME}`. Let us address this in a separate issue. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From duke at openjdk.org Thu Sep 22 17:23:29 2022 From: duke at openjdk.org (SWinxy) Date: Thu, 22 Sep 2022 17:23:29 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Thu, 22 Sep 2022 16:54:39 GMT, Alexey Ivanov wrote: >> src/java.desktop/share/classes/javax/swing/plaf/metal/MetalTheme.java line 68: >> >>> 66: public abstract class MetalTheme { >>> 67: >>> 68: // Constants identifying the various Fonts that a Theme can support >> >> I think this is possibly meant to say "constants that *our* theme can support"? > > Please submit a new JBS issue for it if you can; if you can't, I can submit one on your behalf. > > Possibly it meant to say ?_the_ theme?. I unfortunately don't have a JBS (yet..), so if you could, that would be amazing. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From aivanov at openjdk.org Thu Sep 22 20:22:47 2022 From: aivanov at openjdk.org (Alexey Ivanov) Date: Thu, 22 Sep 2022 20:22:47 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Thu, 22 Sep 2022 17:21:05 GMT, SWinxy wrote: >> Please submit a new JBS issue for it if you can; if you can't, I can submit one on your behalf. >> >> Possibly it meant to say ?_the_ theme?. > > I unfortunately don't have a JBS (yet..), so if you could, that would be amazing. I think the text is correct here: ?that _**a** Theme_ can support `MetalTheme` is a superclass for classes which implement Themes. Thus the constants define fonts which _a particular theme_ may use. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From aivanov at openjdk.org Thu Sep 22 20:22:48 2022 From: aivanov at openjdk.org (Alexey Ivanov) Date: Thu, 22 Sep 2022 20:22:48 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: <8wgnrs5UNZfQxgyoSNxQzjszOCUTxDZY2TGXXUs-1W0=.9ce61a4c-9375-4c80-a4f2-645d7972c96c@github.com> On Thu, 22 Sep 2022 16:59:34 GMT, Alexey Ivanov wrote: >> src/java.desktop/share/classes/sun/awt/SunToolkit.java line 1434: >> >>> 1432: >>> 1433: /** >>> 1434: * Parameterless version of realsync which uses default timeout (see DEFAULT_WAIT_TIME). >> >> Suggestion: >> >> * Parameterless version of realsync which uses the {@link #DEFAULT_WAIT_TIME default timeout}. >> >> I mean this suggestion [might not be warranted](https://github.com/openjdk/jdk/pull/8328/files#r872596373). > > I'm for a clearer message: > > Parameterless version of `{@code realsSync}` which uses _the_ default timeout of `{@link #DEFAULT_WAIT_TIME}`. > > Let us address this in a separate issue. [JDK-8294255](https://bugs.openjdk.org/browse/JDK-8294255): Add link to DEFAULT_WAIT_TIME in javadoc for SunToolKit.realsSync Feel free to provide a patch. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From mernst at openjdk.org Sun Sep 25 17:04:38 2022 From: mernst at openjdk.org (Michael Ernst) Date: Sun, 25 Sep 2022 17:04:38 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: <_zVJ429VO5Y3YZu0eDp_RD4BZRgEOBdDIIBuGf9vH6I=.b17025c7-1e0b-4a1b-a756-3a971b76bd03@github.com> On Thu, 25 Aug 2022 15:35:53 GMT, Michael Ernst wrote: > 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni > If you already are an OpenJDK [Author](https://openjdk.java.net/bylaws#author), [Committer](https://openjdk.java.net/bylaws#committer) or [Reviewer](https://openjdk.java.net/bylaws#reviewer), please click [here](https://bugs.openjdk.java.net/secure/CreateIssue.jspa?pid=11300&issuetype=1) to open a new issue so that we can record that fact. Please use "Add GitHub user mernst" as summary for the issue. Done: https://bugs.openjdk.org/browse/SKARA-1566 ------------- PR: https://git.openjdk.org/jdk/pull/10029 From mernst at openjdk.org Sun Sep 25 17:04:38 2022 From: mernst at openjdk.org (Michael Ernst) Date: Sun, 25 Sep 2022 17:04:38 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni Message-ID: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni ------------- Commit messages: - Remove file that was removed upstream - Fix inconsistency in capitalization - Undo change in zlip - Fix typos Changes: https://git.openjdk.org/jdk/pull/10029/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10029&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8294321 Stats: 317 lines in 108 files changed: 0 ins; 195 del; 122 mod Patch: https://git.openjdk.org/jdk/pull/10029.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10029/head:pull/10029 PR: https://git.openjdk.org/jdk/pull/10029 From jpai at openjdk.org Sun Sep 25 17:04:38 2022 From: jpai at openjdk.org (Jaikiran Pai) Date: Sun, 25 Sep 2022 17:04:38 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: <_zVJ429VO5Y3YZu0eDp_RD4BZRgEOBdDIIBuGf9vH6I=.b17025c7-1e0b-4a1b-a756-3a971b76bd03@github.com> References: <_zVJ429VO5Y3YZu0eDp_RD4BZRgEOBdDIIBuGf9vH6I=.b17025c7-1e0b-4a1b-a756-3a971b76bd03@github.com> Message-ID: On Thu, 25 Aug 2022 19:55:47 GMT, Michael Ernst wrote: >> 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni > >> If you already are an OpenJDK [Author](https://openjdk.java.net/bylaws#author), [Committer](https://openjdk.java.net/bylaws#committer) or [Reviewer](https://openjdk.java.net/bylaws#reviewer), please click [here](https://bugs.openjdk.java.net/secure/CreateIssue.jspa?pid=11300&issuetype=1) to open a new issue so that we can record that fact. Please use "Add GitHub user mernst" as summary for the issue. > > Done: https://bugs.openjdk.org/browse/SKARA-1566 Hello Michael @mernst, these changes are mostly fine. However, they are spread across files which reside in different areas of the JDK. For changes like these, we usually split up the changes into different PRs to help reviewers of specific areas focus on the individual PRs. Would you be willing to split this PR into separate ones. I would recommend starting with one PR which includes changes that are part of `test/jdk/java`, `test/jdk/jdk` and `test/jdk/jni`. If you can come up with that PR, then I'll go ahead and create a JBS issue for it and you can then link the PR against that issue. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From mernst at openjdk.org Sun Sep 25 17:04:38 2022 From: mernst at openjdk.org (Michael Ernst) Date: Sun, 25 Sep 2022 17:04:38 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: <_zVJ429VO5Y3YZu0eDp_RD4BZRgEOBdDIIBuGf9vH6I=.b17025c7-1e0b-4a1b-a756-3a971b76bd03@github.com> Message-ID: On Mon, 5 Sep 2022 06:32:44 GMT, Jaikiran Pai wrote: > these changes are mostly fine. Can you be specific about the exact problems that you noticed that prevented you from saying "these changes are fine"? It doesn't seem useful to make a pull request with known deficiencies. > we usually split up the changes into different PRs to help reviewers of specific areas focus on the individual PRs. Feel free to split up the pull request, if you feel that specific expertise in specific parts of the JDK is necessary to review these changes. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From duke at openjdk.org Sun Sep 25 17:04:39 2022 From: duke at openjdk.org (SWinxy) Date: Sun, 25 Sep 2022 17:04:39 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: <_zVJ429VO5Y3YZu0eDp_RD4BZRgEOBdDIIBuGf9vH6I=.b17025c7-1e0b-4a1b-a756-3a971b76bd03@github.com> Message-ID: On Mon, 5 Sep 2022 14:54:50 GMT, Michael Ernst wrote: > Can you be specific about the exact problems that you noticed that prevented you from saying "these changes are fine"? These changes are fine. I don't see an instance where the duplicated words would mean a change in the specification. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From jpai at openjdk.org Sun Sep 25 17:04:39 2022 From: jpai at openjdk.org (Jaikiran Pai) Date: Sun, 25 Sep 2022 17:04:39 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: On Thu, 25 Aug 2022 15:35:53 GMT, Michael Ernst wrote: > 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni Hello Michael, > > these changes are mostly fine. > > Can you be specific about the exact problems that you noticed that prevented you from saying "these changes are fine"? It doesn't seem useful to make a pull request with known deficiencies. I wasn't implying this PR had deficiencies. What I meant was, to be able to have this reviewed, in addition to code changes this will also need a issue to be created and linked to this PR (and the PR title changed to the form `: `). I have now created https://bugs.openjdk.org/browse/JDK-8294321. Splitting these changes into smaller PRs instead of one big one that touches several different areas of the JDK and 108 files, will help reviewers. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From mernst at openjdk.org Sun Sep 25 17:04:39 2022 From: mernst at openjdk.org (Michael Ernst) Date: Sun, 25 Sep 2022 17:04:39 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: On Sat, 24 Sep 2022 10:41:05 GMT, Jaikiran Pai wrote: > Splitting these changes into smaller PRs instead of one big one that touches several different areas of the JDK and 108 files, will help reviewers. OK. I'll repeat my comment from before: > Feel free to split up the pull request, if you feel that specific expertise in specific parts of the JDK is necessary to review these changes. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From duke at openjdk.org Sun Sep 25 17:04:39 2022 From: duke at openjdk.org (SWinxy) Date: Sun, 25 Sep 2022 17:04:39 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: On Thu, 25 Aug 2022 15:35:53 GMT, Michael Ernst wrote: > 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni Oh no what happened ![image](https://user-images.githubusercontent.com/8303399/192155378-4bb439fa-d27a-417d-8a3c-cf7f7329458f.png) src/java.xml/share/classes/com/sun/org/apache/xpath/internal/NodeSetDTM.java line 1053: > 1051: * fetch will take place at index 1. > 1052: * > 1053: * @return The current position index. Note that there is an inconsistent change here, albeit insignificant. In `NodeSet`, the capital 'The' is removed after the `@return`, while the lowercase 'the' is removed here. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From mernst at openjdk.org Sun Sep 25 17:04:39 2022 From: mernst at openjdk.org (Michael Ernst) Date: Sun, 25 Sep 2022 17:04:39 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: On Sun, 25 Sep 2022 16:51:27 GMT, SWinxy wrote: > Oh no what happened Oops! Thanks for pointing out the goof. It seems to be fixed now. It has now been a month since I opened the pull request, and I have responded to each substantive comment promptly. It would be great to merge this pull request to avoid the need for more merges. > src/java.xml/share/classes/com/sun/org/apache/xpath/internal/NodeSetDTM.java line 1053: > >> 1051: * fetch will take place at index 1. >> 1052: * >> 1053: * @return The current position index. > > Note that there is an inconsistent change here, albeit insignificant. In `NodeSet`, the capital 'The' is removed after the `@return`, while the lowercase 'the' is removed here. Thanks for pointing out the inconsistency. I have fixed it. (I noticed many violations of the official Javadoc style, but this is not the right pull request to fix them.) ------------- PR: https://git.openjdk.org/jdk/pull/10029 From alanb at openjdk.org Sun Sep 25 17:04:40 2022 From: alanb at openjdk.org (Alan Bateman) Date: Sun, 25 Sep 2022 17:04:40 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: On Thu, 25 Aug 2022 15:35:53 GMT, Michael Ernst wrote: > 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni src/java.base/share/native/libzip/zlib/zlib.h line 756: > 754: If this is done, the old level and strategy will be applied to the data > 755: compressed before deflateParams(), and the new level and strategy will be > 756: applied to the data compressed after deflateParams(). This is an issue for the upstream zlib project, we probably don't want to change it here. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From lancea at openjdk.org Sun Sep 25 17:04:40 2022 From: lancea at openjdk.org (Lance Andersen) Date: Sun, 25 Sep 2022 17:04:40 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: On Tue, 30 Aug 2022 09:31:07 GMT, Alan Bateman wrote: >> 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni > > src/java.base/share/native/libzip/zlib/zlib.h line 756: > >> 754: If this is done, the old level and strategy will be applied to the data >> 755: compressed before deflateParams(), and the new level and strategy will be >> 756: applied to the data compressed after deflateParams(). > > This is an issue for the upstream zlib project, we probably don't want to change it here. Agree. See https://github.com/madler/zlib/commit/5752b171fd4cc96b8d1f9526ec1940199c6e9740 which is in the zlib development branch and addresses a wide range of typos. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From mernst at openjdk.org Sun Sep 25 17:04:40 2022 From: mernst at openjdk.org (Michael Ernst) Date: Sun, 25 Sep 2022 17:04:40 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: On Tue, 30 Aug 2022 09:55:18 GMT, Lance Andersen wrote: >> src/java.base/share/native/libzip/zlib/zlib.h line 756: >> >>> 754: If this is done, the old level and strategy will be applied to the data >>> 755: compressed before deflateParams(), and the new level and strategy will be >>> 756: applied to the data compressed after deflateParams(). >> >> This is an issue for the upstream zlib project, we probably don't want to change it here. > > Agree. See https://github.com/madler/zlib/commit/5752b171fd4cc96b8d1f9526ec1940199c6e9740 which is in the zlib development branch and addresses a wide range of typos. OK. I backed out the change to zlib. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From duke at openjdk.org Sun Sep 25 17:23:28 2022 From: duke at openjdk.org (SWinxy) Date: Sun, 25 Sep 2022 17:23:28 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: On Thu, 25 Aug 2022 15:35:53 GMT, Michael Ernst wrote: > 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni I'm not a committer (yet) so I can't [sponsor](https://openjdk.org/sponsor/) this PR, even though I would. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From joehw at openjdk.org Mon Sep 26 16:16:34 2022 From: joehw at openjdk.org (Joe Wang) Date: Mon, 26 Sep 2022 16:16:34 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni In-Reply-To: References: Message-ID: On Thu, 25 Aug 2022 15:35:53 GMT, Michael Ernst wrote: > 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni We have discussed several times in the past that we don't touch upstream (in this case, Apache) code unless the change is essential. In general, if you fix a bug in a class, it's fine to fix other non-essential things within the class, such as code styles, javadocs, typos as in this case, etc. Otherwise, I would suggest you contribute such changes to the upstream projects. Thanks. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From duke at openjdk.org Mon Sep 26 16:41:42 2022 From: duke at openjdk.org (SWinxy) Date: Mon, 26 Sep 2022 16:41:42 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Wed, 21 Sep 2022 11:52:57 GMT, Magnus Ihse Bursie wrote: >> I ran `codespell` on the `src/java.desktop` directory, and accepted those changes where it indeed discovered real typos. >> >> I ignored typos in public methods and variables. Maybe they can be fixed later on without much fanfare, if they are in internal classes. Typos in exposed APIs are likely here to stay. >> >> I will update copyright years using a script before pushing (otherwise like every second change would be a copyright update, making reviewing much harder). >> >> The long term goal here is to make tooling support for running `codespell`. The trouble with automating this is of course all false positives. But before even trying to solve that issue, all true positives must be fixed. Hence this PR. > > Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 49 commits: > > - Merge branch 'master' into typos-in-java.desktop > - Revert changes to glext.h > - Revert changes to multiVis.c and wsutils.h > - Merge branch 'master' into typos-in-java.desktop > - Revert changes in libjpeg > - Revert changes in libfreetype > - Update src/java.desktop/windows/classes/sun/awt/windows/WPrinterJob.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/unix/classes/sun/awt/X11/XBaseMenuWindow.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - Update src/java.desktop/share/classes/sun/swing/SwingUtilities2.java > > Co-authored-by: Alexey Ivanov <70774172+aivanov-jdk at users.noreply.github.com> > - ... and 39 more: https://git.openjdk.org/jdk/compare/cddd6def...2850610d Marked as reviewed by SWinxy at github.com (no known OpenJDK username). ------------- PR: https://git.openjdk.org/jdk/pull/8328 From duke at openjdk.org Mon Sep 26 16:41:42 2022 From: duke at openjdk.org (SWinxy) Date: Mon, 26 Sep 2022 16:41:42 GMT Subject: RFR: 8285306: Fix typos in java.desktop [v10] In-Reply-To: References: <5gAPAoRiIJr6BEko1UEaMd3QeUte-snqvfc9eNU2Jgk=.a6d39dcd-0d89-4444-a890-a6c53f41245b@github.com> Message-ID: On Thu, 22 Sep 2022 20:19:12 GMT, Alexey Ivanov wrote: >> I unfortunately don't have a JBS (yet..), so if you could, that would be amazing. > > I think the text is correct here: ?that _**a** Theme_ can support > > `MetalTheme` is a superclass for classes which implement Themes. Thus the constants define fonts which _a particular theme_ may use. Makes sense. ------------- PR: https://git.openjdk.org/jdk/pull/8328 From mernst at openjdk.org Mon Sep 26 16:51:36 2022 From: mernst at openjdk.org (Michael Ernst) Date: Mon, 26 Sep 2022 16:51:36 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni [v2] In-Reply-To: References: Message-ID: > 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni Michael Ernst has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains six commits: - Reinstate typos in Apache code that is copied into the JDK - Merge ../jdk-openjdk into typos-typos - Remove file that was removed upstream - Fix inconsistency in capitalization - Undo change in zlip - Fix typos ------------- Changes: https://git.openjdk.org/jdk/pull/10029/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10029&range=01 Stats: 85 lines in 76 files changed: 0 ins; 0 del; 85 mod Patch: https://git.openjdk.org/jdk/pull/10029.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10029/head:pull/10029 PR: https://git.openjdk.org/jdk/pull/10029 From joehw at openjdk.org Mon Sep 26 17:04:25 2022 From: joehw at openjdk.org (Joe Wang) Date: Mon, 26 Sep 2022 17:04:25 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni [v2] In-Reply-To: References: Message-ID: On Mon, 26 Sep 2022 16:51:36 GMT, Michael Ernst wrote: >> 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni > > Michael Ernst has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains six commits: > > - Reinstate typos in Apache code that is copied into the JDK > - Merge ../jdk-openjdk into typos-typos > - Remove file that was removed upstream > - Fix inconsistency in capitalization > - Undo change in zlip > - Fix typos Thanks for the update! ------------- PR: https://git.openjdk.org/jdk/pull/10029 From lancea at openjdk.org Mon Sep 26 19:38:20 2022 From: lancea at openjdk.org (Lance Andersen) Date: Mon, 26 Sep 2022 19:38:20 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni [v2] In-Reply-To: References: Message-ID: <3PJ-Gv4AW5nTD3gcQ1mwZH5C0jFo09zD6879B3jlkY4=.05beeb4b-498d-40fb-8514-244ac0ef0772@github.com> On Mon, 26 Sep 2022 16:51:36 GMT, Michael Ernst wrote: >> 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni > > Michael Ernst has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains six commits: > > - Reinstate typos in Apache code that is copied into the JDK > - Merge ../jdk-openjdk into typos-typos > - Remove file that was removed upstream > - Fix inconsistency in capitalization > - Undo change in zlip > - Fix typos Thank you for your efforts on the cleaning up these typos I would suggest breaking these changes into separate PRs by team as there seems to be changes to hotspot, core-libs, and client to make it easier to review. I realize the changes are fairly trivial but this will most likely expedite getting your changes back ------------- PR: https://git.openjdk.org/jdk/pull/10029 From duke at openjdk.org Mon Sep 26 22:17:41 2022 From: duke at openjdk.org (Justin Lu) Date: Mon, 26 Sep 2022 22:17:41 GMT Subject: RFR: 8272687: Replace StringBuffer with StringBuilder in RuleBasedCollator Message-ID: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> Problem: Unnecessary instances of StringBuffer + .toString() Fix: StringBuffer Replaced with StringBuilder, and .toString() removed when possible Other: Line 698 in RuleBasedCollator.java also uses a .toString() conversion, but removing that instance requires changing the RuleBasedCollationKey constructor's second parameter type from String to StringBuilder automated testing run passed cleanly ------------- Commit messages: - Copyright update for fix - Merge master into fix branch - Fix: replace instances of StringBuffer with StringBuilder, drop String conversion Changes: https://git.openjdk.org/jdk/pull/10432/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10432&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8272687 Stats: 10 lines in 2 files changed: 0 ins; 0 del; 10 mod Patch: https://git.openjdk.org/jdk/pull/10432.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10432/head:pull/10432 PR: https://git.openjdk.org/jdk/pull/10432 From lancea at openjdk.org Mon Sep 26 22:17:41 2022 From: lancea at openjdk.org (Lance Andersen) Date: Mon, 26 Sep 2022 22:17:41 GMT Subject: RFR: 8272687: Replace StringBuffer with StringBuilder in RuleBasedCollator In-Reply-To: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> References: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> Message-ID: On Mon, 26 Sep 2022 18:25:34 GMT, Justin Lu wrote: > Problem: Unnecessary instances of StringBuffer + .toString() > > Fix: StringBuffer Replaced with StringBuilder, and .toString() removed when possible > > Other: Line 698 in RuleBasedCollator.java also uses a .toString() conversion, but removing that instance requires changing the RuleBasedCollationKey constructor's second parameter type from String to StringBuilder > > automated testing run passed cleanly The changes look good Justin. ------------- Marked as reviewed by lancea (Reviewer). PR: https://git.openjdk.org/jdk/pull/10432 From naoto at openjdk.org Mon Sep 26 22:17:41 2022 From: naoto at openjdk.org (Naoto Sato) Date: Mon, 26 Sep 2022 22:17:41 GMT Subject: RFR: 8272687: Replace StringBuffer with StringBuilder in RuleBasedCollator In-Reply-To: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> References: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> Message-ID: <9wwdMSrZ0ie0sGXoxDcX9XWLL7Syb-Z2jqvaj3qlTwE=.a2cc6270-a657-4aa2-97ff-4f91925de043@github.com> On Mon, 26 Sep 2022 18:25:34 GMT, Justin Lu wrote: > Problem: Unnecessary instances of StringBuffer + .toString() > > Fix: StringBuffer Replaced with StringBuilder, and .toString() removed when possible > > Other: Line 698 in RuleBasedCollator.java also uses a .toString() conversion, but removing that instance requires changing the RuleBasedCollationKey constructor's second parameter type from String to StringBuilder > > automated testing run passed cleanly Marked as reviewed by naoto (Reviewer). ------------- PR: https://git.openjdk.org/jdk/pull/10432 From bchristi at openjdk.org Mon Sep 26 22:17:41 2022 From: bchristi at openjdk.org (Brent Christian) Date: Mon, 26 Sep 2022 22:17:41 GMT Subject: RFR: 8272687: Replace StringBuffer with StringBuilder in RuleBasedCollator In-Reply-To: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> References: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> Message-ID: On Mon, 26 Sep 2022 18:25:34 GMT, Justin Lu wrote: > Problem: Unnecessary instances of StringBuffer + .toString() > > Fix: StringBuffer Replaced with StringBuilder, and .toString() removed when possible > > Other: Line 698 in RuleBasedCollator.java also uses a .toString() conversion, but removing that instance requires changing the RuleBasedCollationKey constructor's second parameter type from String to StringBuilder > > automated testing run passed cleanly Looks good! ------------- Marked as reviewed by bchristi (Reviewer). PR: https://git.openjdk.org/jdk/pull/10432 From bpb at openjdk.org Mon Sep 26 22:23:45 2022 From: bpb at openjdk.org (Brian Burkhalter) Date: Mon, 26 Sep 2022 22:23:45 GMT Subject: RFR: 8272687: Replace StringBuffer with StringBuilder in RuleBasedCollator In-Reply-To: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> References: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> Message-ID: On Mon, 26 Sep 2022 18:25:34 GMT, Justin Lu wrote: > Problem: Unnecessary instances of StringBuffer + .toString() > > Fix: StringBuffer Replaced with StringBuilder, and .toString() removed when possible > > Other: Line 698 in RuleBasedCollator.java also uses a .toString() conversion, but removing that instance requires changing the RuleBasedCollationKey constructor's second parameter type from String to StringBuilder > > automated testing run passed cleanly Marked as reviewed by bpb (Reviewer). ------------- PR: https://git.openjdk.org/jdk/pull/10432 From duke at openjdk.org Mon Sep 26 22:34:40 2022 From: duke at openjdk.org (Justin Lu) Date: Mon, 26 Sep 2022 22:34:40 GMT Subject: Integrated: 8272687: Replace StringBuffer with StringBuilder in RuleBasedCollator In-Reply-To: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> References: <6FHBd4vRdnguVSgq1IM3wg569qKcwmgUyPFSDGTDfdU=.9591d145-88c4-4d57-bb34-5b0a12b5e46c@github.com> Message-ID: <2R35rpu5H3silZ4Neb4dhA5qnS6y0PUivFH17OgYUTQ=.ffca51b2-95f8-48b2-acaa-c385b73216ec@github.com> On Mon, 26 Sep 2022 18:25:34 GMT, Justin Lu wrote: > Problem: Unnecessary instances of StringBuffer + .toString() > > Fix: StringBuffer Replaced with StringBuilder, and .toString() removed when possible > > Other: Line 698 in RuleBasedCollator.java also uses a .toString() conversion, but removing that instance requires changing the RuleBasedCollationKey constructor's second parameter type from String to StringBuilder > > automated testing run passed cleanly This pull request has now been integrated. Changeset: 43eff2b3 Author: Justin Lu Committer: Brent Christian URL: https://git.openjdk.org/jdk/commit/43eff2b309e2ef275bdd5adf196da81d4e23f535 Stats: 10 lines in 2 files changed: 0 ins; 0 del; 10 mod 8272687: Replace StringBuffer with StringBuilder in RuleBasedCollator Reviewed-by: lancea, naoto, bchristi, bpb ------------- PR: https://git.openjdk.org/jdk/pull/10432 From aturbanov at openjdk.org Tue Sep 27 19:21:09 2022 From: aturbanov at openjdk.org (Andrey Turbanov) Date: Tue, 27 Sep 2022 19:21:09 GMT Subject: RFR: 8294472: Remove redundant rawtypes suppression in AbstractChronology Message-ID: Found this redundant suppressions by IntelliJ IDEA inspection. Seems initially `Chronology` was generic class? ------------- Commit messages: - [PATCH] Remove redundant rawtypes suppression in AbstractChronology Changes: https://git.openjdk.org/jdk/pull/10433/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10433&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8294472 Stats: 7 lines in 1 file changed: 0 ins; 5 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/10433.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10433/head:pull/10433 PR: https://git.openjdk.org/jdk/pull/10433 From lancea at openjdk.org Tue Sep 27 19:40:16 2022 From: lancea at openjdk.org (Lance Andersen) Date: Tue, 27 Sep 2022 19:40:16 GMT Subject: RFR: 8294472: Remove redundant rawtypes suppression in AbstractChronology In-Reply-To: References: Message-ID: On Mon, 26 Sep 2022 19:12:16 GMT, Andrey Turbanov wrote: > Found this redundant suppressions by IntelliJ IDEA inspection. > Seems initially `Chronology` was generic class? Marked as reviewed by lancea (Reviewer). ------------- PR: https://git.openjdk.org/jdk/pull/10433 From naoto at openjdk.org Tue Sep 27 20:45:32 2022 From: naoto at openjdk.org (Naoto Sato) Date: Tue, 27 Sep 2022 20:45:32 GMT Subject: RFR: 8294472: Remove redundant rawtypes suppression in AbstractChronology In-Reply-To: References: Message-ID: On Mon, 26 Sep 2022 19:12:16 GMT, Andrey Turbanov wrote: > Found this redundant suppressions by IntelliJ IDEA inspection. > Seems initially `Chronology` was generic class? +1 ------------- Marked as reviewed by naoto (Reviewer). PR: https://git.openjdk.org/jdk/pull/10433 From mernst at openjdk.org Tue Sep 27 23:16:16 2022 From: mernst at openjdk.org (Michael Ernst) Date: Tue, 27 Sep 2022 23:16:16 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni [v2] In-Reply-To: <3PJ-Gv4AW5nTD3gcQ1mwZH5C0jFo09zD6879B3jlkY4=.05beeb4b-498d-40fb-8514-244ac0ef0772@github.com> References: <3PJ-Gv4AW5nTD3gcQ1mwZH5C0jFo09zD6879B3jlkY4=.05beeb4b-498d-40fb-8514-244ac0ef0772@github.com> Message-ID: <1UZcv-X4dxQHlgj8b5B2sGJ9NpxWrOp1EwbWeazjj2I=.1cf2b14f-7064-47b6-8d25-887732020bb0@github.com> On Mon, 26 Sep 2022 19:36:02 GMT, Lance Andersen wrote: > Thank you for your efforts on the cleaning up these typos > > I would suggest breaking these changes into separate PRs by team as there seems to be changes to hotspot, core-libs, and client to make it easier to review. > > I realize the changes are fairly trivial but this will most likely expedite getting your changes back Feel free to break up the pull request if that is what is needed to free it from red tape. Thanks. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From dfuchs at openjdk.org Wed Sep 28 13:24:26 2022 From: dfuchs at openjdk.org (Daniel Fuchs) Date: Wed, 28 Sep 2022 13:24:26 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni [v2] In-Reply-To: <1UZcv-X4dxQHlgj8b5B2sGJ9NpxWrOp1EwbWeazjj2I=.1cf2b14f-7064-47b6-8d25-887732020bb0@github.com> References: <3PJ-Gv4AW5nTD3gcQ1mwZH5C0jFo09zD6879B3jlkY4=.05beeb4b-498d-40fb-8514-244ac0ef0772@github.com> <1UZcv-X4dxQHlgj8b5B2sGJ9NpxWrOp1EwbWeazjj2I=.1cf2b14f-7064-47b6-8d25-887732020bb0@github.com> Message-ID: On Tue, 27 Sep 2022 23:12:43 GMT, Michael Ernst wrote: > Feel free to break up the pull request if that is what is needed to free it from red tape. Only you can do that @mernst ------------- PR: https://git.openjdk.org/jdk/pull/10029 From mernst at openjdk.org Wed Sep 28 14:49:20 2022 From: mernst at openjdk.org (Michael Ernst) Date: Wed, 28 Sep 2022 14:49:20 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni [v2] In-Reply-To: References: Message-ID: On Mon, 26 Sep 2022 16:51:36 GMT, Michael Ernst wrote: >> 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni > > Michael Ernst has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains six commits: > > - Reinstate typos in Apache code that is copied into the JDK > - Merge ../jdk-openjdk into typos-typos > - Remove file that was removed upstream > - Fix inconsistency in capitalization > - Undo change in zlip > - Fix typos Regarding breaking up the pull request: * No one has stated that this is actually necessary or given a guarantee that it will result in a merged pull request, only that it *might* finally free this pull request of red tape. * I have spent a nontrivial amount of time on these fixes. There have been long delays, which forced me to resolve merge conflicts. I was told that the changes are "mostly fine" without any indication of what is wrong. I am reluctant to spend yet more time, only to later (maybe weeks later, as has already happened) find out that I still have to do something else or that all my effort was wasted. * No one has explained what to do. "separate PRs by team" doesn't tell me what to do, since I don't see an org chart anywhere in the documentation that tells me what a "team" is. I'm sorry to state it so bluntly, but this is not a good look for the JDK team being welcoming to corrections. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From dfuchs at openjdk.org Wed Sep 28 15:13:39 2022 From: dfuchs at openjdk.org (Daniel Fuchs) Date: Wed, 28 Sep 2022 15:13:39 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni [v2] In-Reply-To: References: Message-ID: On Wed, 28 Sep 2022 14:45:54 GMT, Michael Ernst wrote: >> Michael Ernst has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains six commits: >> >> - Reinstate typos in Apache code that is copied into the JDK >> - Merge ../jdk-openjdk into typos-typos >> - Remove file that was removed upstream >> - Fix inconsistency in capitalization >> - Undo change in zlip >> - Fix typos > > Regarding breaking up the pull request: > * No one has stated that this is actually necessary or given a guarantee that it will result in a merged pull request, only that it *might* finally free this pull request of red tape. > * Despite my repeated requests, no one has justified that *this particular pull request* needs the expertise of different teams. The only reasons stated have been custom and bureaucracy. > * I have spent a nontrivial amount of time on these fixes. There have been long delays, which forced me to resolve merge conflicts. I was told that the changes are "mostly fine" without any indication of what is wrong. I am reluctant to spend yet more time, only to later (maybe weeks later, as has already happened) find out that I still have to do something else or that all my effort was wasted. > * I was condescendingly told "We have discussed several times in the past ..." even though I was not privy to those discussions. No pointer to documentation in the JDK itself, about pull requests, was given. > * No one has explained what to do. "separate PRs by team" doesn't tell me what to do, since I don't see an org chart anywhere in the documentation that tells me what a "team" is. > > I'm sorry to state it so bluntly, but this is not a good look for the JDK team being welcoming to contributions. Hi @mernst, sorry if this is how it appears. Pull requests that involve changes spanning a large set of files are notoriously harder to review since they require a reviewer from each different area to chime in. Basically you will need one reviewer from each of these areas: - client - compiler - core-libs - hotspot - i18n - javadoc - jmx - net - nio - security - serviceability Jaikiran suggested to reduce the scope of this PR in his first comment: https://github.com/openjdk/jdk/pull/10029#issuecomment-1236588632 as did several other reviewers. Sorry if the meaning (or reason) was not clear. best regards, ------------- PR: https://git.openjdk.org/jdk/pull/10029 From aivanov at openjdk.org Wed Sep 28 15:28:24 2022 From: aivanov at openjdk.org (Alexey Ivanov) Date: Wed, 28 Sep 2022 15:28:24 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni [v2] In-Reply-To: References: Message-ID: On Mon, 26 Sep 2022 16:51:36 GMT, Michael Ernst wrote: >> 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni > > Michael Ernst has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains six commits: > > - Reinstate typos in Apache code that is copied into the JDK > - Merge ../jdk-openjdk into typos-typos > - Remove file that was removed upstream > - Fix inconsistency in capitalization > - Undo change in zlip > - Fix typos The title says under `test/jdk/*`, yet there are lots of files changed in `src/*`. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From mernst at openjdk.org Wed Sep 28 15:35:40 2022 From: mernst at openjdk.org (Michael Ernst) Date: Wed, 28 Sep 2022 15:35:40 GMT Subject: RFR: 8294321: Fix typos in files under test/jdk/java, test/jdk/jdk, test/jdk/jni [v2] In-Reply-To: References: Message-ID: On Wed, 28 Sep 2022 15:26:13 GMT, Alexey Ivanov wrote: > The title says under `test/jdk/*`, yet there are lots of files changed in `src/*`. The title was edited by someone other than me, as you can see from the PR history. ------------- PR: https://git.openjdk.org/jdk/pull/10029 From aturbanov at openjdk.org Wed Sep 28 18:47:22 2022 From: aturbanov at openjdk.org (Andrey Turbanov) Date: Wed, 28 Sep 2022 18:47:22 GMT Subject: Integrated: 8294472: Remove redundant rawtypes suppression in AbstractChronology In-Reply-To: References: Message-ID: On Mon, 26 Sep 2022 19:12:16 GMT, Andrey Turbanov wrote: > Found this redundant suppressions by IntelliJ IDEA inspection. > Seems initially `Chronology` was generic class? This pull request has now been integrated. Changeset: 9309786d Author: Andrey Turbanov URL: https://git.openjdk.org/jdk/commit/9309786dbfa584e7762c8011e3942f02d352d2e6 Stats: 7 lines in 1 file changed: 0 ins; 5 del; 2 mod 8294472: Remove redundant rawtypes suppression in AbstractChronology Reviewed-by: lancea, naoto ------------- PR: https://git.openjdk.org/jdk/pull/10433 From duke at openjdk.org Thu Sep 29 21:27:02 2022 From: duke at openjdk.org (Justin Lu) Date: Thu, 29 Sep 2022 21:27:02 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text Message-ID: Problem: Unnecessary instances of StringBuffer within java.text (internal only) Fix: StringBuffer Replaced with StringBuilder, and adjusted variable/method names ------------- Commit messages: - Update PatternEntry test case for StringBuilder - Copyright update - Replace buffer in both, adjust addToBuilder dependencies - Adjust variable names within DigitList - Fix: Replace StringBuffer in CollationElementIterator - Fix: replace StringBuffer with StringBuilder Changes: https://git.openjdk.org/jdk/pull/10475/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10475&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8294397 Stats: 35 lines in 5 files changed: 0 ins; 0 del; 35 mod Patch: https://git.openjdk.org/jdk/pull/10475.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10475/head:pull/10475 PR: https://git.openjdk.org/jdk/pull/10475 From lancea at openjdk.org Thu Sep 29 21:38:20 2022 From: lancea at openjdk.org (Lance Andersen) Date: Thu, 29 Sep 2022 21:38:20 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text In-Reply-To: References: Message-ID: On Wed, 28 Sep 2022 22:54:33 GMT, Justin Lu wrote: > Problem: Unnecessary instances of StringBuffer within java.text (internal only) > > Fix: StringBuffer Replaced with StringBuilder, and adjusted variable/method names Looks good. should we update test/jdk/sun/text/IntHashtable/patch-src/java.base/java/text/Bug4170614Test.java to include `@test, @bug, @run, @summary`? ------------- Marked as reviewed by lancea (Reviewer). PR: https://git.openjdk.org/jdk/pull/10475 From duke at openjdk.org Thu Sep 29 21:51:43 2022 From: duke at openjdk.org (Justin Lu) Date: Thu, 29 Sep 2022 21:51:43 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text In-Reply-To: References: Message-ID: On Thu, 29 Sep 2022 21:34:24 GMT, Lance Andersen wrote: > should we update test/jdk/sun/text/IntHashtable/patch-src/java.base/java/text/Bug4170614Test.java to include `@test, @bug, @run, @summary`? Brent actually pointed that out to me as well. I believe since Bug4170614Test.java is managed by Bug4170614TestRun.java which has tags, then it would be fine to not include the tags(in Bug4170614Test.java), but please let me know your thoughts. @LanceAndersen ------------- PR: https://git.openjdk.org/jdk/pull/10475 From bchristi at openjdk.org Thu Sep 29 21:51:43 2022 From: bchristi at openjdk.org (Brent Christian) Date: Thu, 29 Sep 2022 21:51:43 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text In-Reply-To: References: Message-ID: <0V9OZIDGjTl4mNUFSqeGQXRZUzG8hIBLjixuoISbS1I=.c5c0d643-2e83-4870-b27e-fae90e16aafb@github.com> On Thu, 29 Sep 2022 21:48:52 GMT, Justin Lu wrote: > should we update test/jdk/sun/text/IntHashtable/patch-src/java.base/java/text/Bug4170614Test.java to include `@test, @bug, @run, @summary`? /* (this test doesn't have an at-test tag because it's run by Bug4170614TestRun.java instead of directly by the test harness) */ :) ------------- PR: https://git.openjdk.org/jdk/pull/10475 From lancea at openjdk.org Thu Sep 29 21:58:21 2022 From: lancea at openjdk.org (Lance Andersen) Date: Thu, 29 Sep 2022 21:58:21 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text In-Reply-To: <0V9OZIDGjTl4mNUFSqeGQXRZUzG8hIBLjixuoISbS1I=.c5c0d643-2e83-4870-b27e-fae90e16aafb@github.com> References: <0V9OZIDGjTl4mNUFSqeGQXRZUzG8hIBLjixuoISbS1I=.c5c0d643-2e83-4870-b27e-fae90e16aafb@github.com> Message-ID: <9_WnJ6L0hddDDWuv0_ePWSASObEVohCHIJqCCRacFvw=.9cae45d1-5d97-423e-96ee-aeed57c78ecd@github.com> On Thu, 29 Sep 2022 21:49:05 GMT, Brent Christian wrote: > > should we update test/jdk/sun/text/IntHashtable/patch-src/java.base/java/text/Bug4170614Test.java to include `@test, @bug, @run, @summary`? > > ``` > /* > (this test doesn't have an at-test tag because it's run by Bug4170614TestRun.java > instead of directly by the test harness) > */ > ``` > > :) Justin, Brent Thanks for pointing that out. Do either of you know why this is configured as it is as I am not sure I see a reason for the wrapper? ------------- PR: https://git.openjdk.org/jdk/pull/10475 From naoto at openjdk.org Thu Sep 29 22:12:30 2022 From: naoto at openjdk.org (Naoto Sato) Date: Thu, 29 Sep 2022 22:12:30 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text In-Reply-To: References: Message-ID: On Wed, 28 Sep 2022 22:54:33 GMT, Justin Lu wrote: > Problem: Unnecessary instances of StringBuffer within java.text (internal only) > > Fix: StringBuffer Replaced with StringBuilder, and adjusted variable/method names AFAICT, the reason is described in the test class description, i.e., tweak to be in `java.text` package so that it can test the internal `hashCode` method. btw I find a typo there: * Bug #4170614 complained that we had two iternal classes that ------------- PR: https://git.openjdk.org/jdk/pull/10475 From duke at openjdk.org Thu Sep 29 22:15:00 2022 From: duke at openjdk.org (Justin Lu) Date: Thu, 29 Sep 2022 22:15:00 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text [v2] In-Reply-To: References: Message-ID: > Problem: Unnecessary instances of StringBuffer within java.text (internal only) > > Fix: StringBuffer Replaced with StringBuilder, and adjusted variable/method names Justin Lu has updated the pull request incrementally with one additional commit since the last revision: Adjust typo within test description ------------- Changes: - all: https://git.openjdk.org/jdk/pull/10475/files - new: https://git.openjdk.org/jdk/pull/10475/files/ea2bc5e7..e02edf67 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=10475&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=10475&range=00-01 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/10475.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10475/head:pull/10475 PR: https://git.openjdk.org/jdk/pull/10475 From lancea at openjdk.org Thu Sep 29 22:26:35 2022 From: lancea at openjdk.org (Lance Andersen) Date: Thu, 29 Sep 2022 22:26:35 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text [v2] In-Reply-To: References: Message-ID: On Thu, 29 Sep 2022 22:15:00 GMT, Justin Lu wrote: >> Problem: Unnecessary instances of StringBuffer within java.text (internal only) >> >> Fix: StringBuffer Replaced with StringBuilder, and adjusted variable/method names > > Justin Lu has updated the pull request incrementally with one additional commit since the last revision: > > Adjust typo within test description Marked as reviewed by lancea (Reviewer). > > should we update test/jdk/sun/text/IntHashtable/patch-src/java.base/java/text/Bug4170614Test.java to include `@test, @bug, @run, @summary`? > > Brent actually pointed that out to me as well. I believe since Bug4170614Test.java is managed by Bug4170614TestRun.java which has tags, then it would be fine to not include the tags(in Bug4170614Test.java), but please let me know your thoughts. @LanceAndersen > > should we update test/jdk/sun/text/IntHashtable/patch-src/java.base/java/text/Bug4170614Test.java to include `@test, @bug, @run, @summary`? > > Brent actually pointed that out to me as well. I believe since Bug4170614Test.java is managed by Bug4170614TestRun.java which has tags, then it would be fine to not include the tags(in Bug4170614Test.java), but please let me know your thoughts. @LanceAndersen Hi Justin, Yes if the wrapper class is needed then we do not need the tags in the actual test. ------------- PR: https://git.openjdk.org/jdk/pull/10475 From lancea at openjdk.org Thu Sep 29 22:26:35 2022 From: lancea at openjdk.org (Lance Andersen) Date: Thu, 29 Sep 2022 22:26:35 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text In-Reply-To: References: Message-ID: On Thu, 29 Sep 2022 22:07:48 GMT, Naoto Sato wrote: > AFAICT, the reason is described in the test class description, i.e., tweak to be in `java.text` package so that it can test the internal `hashCode` method. Understand, I guess I don't see the difference from moving the tags to the actual test but there could be a subtlety I am missing (wouldn't be the first time ;-) ) ------------- PR: https://git.openjdk.org/jdk/pull/10475 From naoto at openjdk.org Thu Sep 29 22:34:19 2022 From: naoto at openjdk.org (Naoto Sato) Date: Thu, 29 Sep 2022 22:34:19 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text In-Reply-To: References: Message-ID: <4-c7dC9feD9vgVdjtLf3rgcmBi6yM2kvYErlwzqvDhQ=.2dce9d38-d3af-4038-8ba9-ce462191ddd1@github.com> On Thu, 29 Sep 2022 22:19:26 GMT, Lance Andersen wrote: > Understand, I guess I don't see the difference from moving the tags to the actual test but there could be a subtlety I am missing (wouldn't be the first time ;-) ) The runner has a @library/@build tag to build the test case as a library for the said reason. ------------- PR: https://git.openjdk.org/jdk/pull/10475 From bchristi at openjdk.org Thu Sep 29 22:34:24 2022 From: bchristi at openjdk.org (Brent Christian) Date: Thu, 29 Sep 2022 22:34:24 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text [v2] In-Reply-To: References: Message-ID: <7R_FJi6DYp4rE7nHNvpW6LPOsa5L_e7ul1ii1t8QeIA=.a8628f49-e0ce-41ee-8c7e-4e8f7faf983e@github.com> On Thu, 29 Sep 2022 22:15:00 GMT, Justin Lu wrote: >> Problem: Unnecessary instances of StringBuffer within java.text (internal only) >> >> Fix: StringBuffer Replaced with StringBuilder, and adjusted variable/method names > > Justin Lu has updated the pull request incrementally with one additional commit since the last revision: > > Adjust typo within test description src/java.base/share/classes/java/text/DigitList.java line 808: > 806: } > 807: return tempBuilder; > 808: } Is it worth considering whether it's still necessary to cache and reuse a single String[Buffer|Builder] instance when using 2022 garbage collectors? src/java.base/share/classes/java/text/PatternEntry.java line 117: > 115: boolean showExtension, > 116: boolean showWhiteSpace, > 117: PatternEntry lastEntry) Nit: update the indentation on these lines src/java.base/share/classes/java/text/PatternEntry.java line 291: > 289: // We re-use these objects in order to improve performance > 290: private StringBuilder newChars = new StringBuilder(); > 291: private StringBuilder newExtension = new StringBuilder(); Again, in 2022, I don't know that this cache+reuse pattern is needed for performance. ------------- PR: https://git.openjdk.org/jdk/pull/10475 From duke at openjdk.org Thu Sep 29 22:44:43 2022 From: duke at openjdk.org (Justin Lu) Date: Thu, 29 Sep 2022 22:44:43 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text [v3] In-Reply-To: References: Message-ID: > Problem: Unnecessary instances of StringBuffer within java.text (internal only) > > Fix: StringBuffer Replaced with StringBuilder, and adjusted variable/method names Justin Lu has updated the pull request incrementally with one additional commit since the last revision: Tweak indentation in PaternEntry ------------- Changes: - all: https://git.openjdk.org/jdk/pull/10475/files - new: https://git.openjdk.org/jdk/pull/10475/files/e02edf67..cd966f31 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=10475&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=10475&range=01-02 Stats: 3 lines in 1 file changed: 0 ins; 0 del; 3 mod Patch: https://git.openjdk.org/jdk/pull/10475.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10475/head:pull/10475 PR: https://git.openjdk.org/jdk/pull/10475 From duke at openjdk.org Fri Sep 30 00:03:35 2022 From: duke at openjdk.org (Justin Lu) Date: Fri, 30 Sep 2022 00:03:35 GMT Subject: RFR: 8294307: ISO 4217 Amendment 173 Update Message-ID: Problem: Amendment number outdated Fix: Update amendment number + date in properties file and test case data file ------------- Commit messages: - Update amendment number in test case data file - Update amendment number Changes: https://git.openjdk.org/jdk/pull/10499/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10499&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8294307 Stats: 4 lines in 2 files changed: 0 ins; 0 del; 4 mod Patch: https://git.openjdk.org/jdk/pull/10499.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10499/head:pull/10499 PR: https://git.openjdk.org/jdk/pull/10499 From lancea at openjdk.org Fri Sep 30 00:21:36 2022 From: lancea at openjdk.org (Lance Andersen) Date: Fri, 30 Sep 2022 00:21:36 GMT Subject: RFR: 8294307: ISO 4217 Amendment 173 Update In-Reply-To: References: Message-ID: <57AQADcwjE5ew8vvvRKjcfW9l5HgzXGaPdEK-T_jC-k=.0b6f11a6-ac0d-44ea-ba92-88312b6d1f29@github.com> On Thu, 29 Sep 2022 23:19:16 GMT, Justin Lu wrote: > Problem: Amendment number outdated > > Fix: Update amendment number + date in properties file and test case data file looks good to me ------------- Marked as reviewed by lancea (Reviewer). PR: https://git.openjdk.org/jdk/pull/10499 From lancea at openjdk.org Fri Sep 30 00:29:17 2022 From: lancea at openjdk.org (Lance Andersen) Date: Fri, 30 Sep 2022 00:29:17 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text In-Reply-To: <4-c7dC9feD9vgVdjtLf3rgcmBi6yM2kvYErlwzqvDhQ=.2dce9d38-d3af-4038-8ba9-ce462191ddd1@github.com> References: <4-c7dC9feD9vgVdjtLf3rgcmBi6yM2kvYErlwzqvDhQ=.2dce9d38-d3af-4038-8ba9-ce462191ddd1@github.com> Message-ID: On Thu, 29 Sep 2022 22:29:10 GMT, Naoto Sato wrote: > > Understand, I guess I don't see the difference from moving the tags to the actual test but there could be a subtlety I am missing (wouldn't be the first time ;-) ) > > The runner has a @library/@build tag to build the test case as a library for the said reason. Ok, thanks Naoto ------------- PR: https://git.openjdk.org/jdk/pull/10475 From ysatowse at openjdk.org Fri Sep 30 00:36:54 2022 From: ysatowse at openjdk.org (Yoshiki Sato) Date: Fri, 30 Sep 2022 00:36:54 GMT Subject: RFR: 8294357: (tz) Update Timezone Data to 2022d Message-ID: Please review this PR. The change include some code changes in ZoneInfoFile.java and TestZoneInfo310.java since tzdata2022d breaks TestZoneInfo310.java. ------------- Commit messages: - Added minor changes in comment lines - reverting irrelvant change in pom.xml - 1st commit for tz2022d Changes: https://git.openjdk.org/jdk/pull/10460/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10460&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8294357 Stats: 105 lines in 11 files changed: 31 ins; 55 del; 19 mod Patch: https://git.openjdk.org/jdk/pull/10460.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10460/head:pull/10460 PR: https://git.openjdk.org/jdk/pull/10460 From naoto at openjdk.org Fri Sep 30 00:36:54 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 30 Sep 2022 00:36:54 GMT Subject: RFR: 8294357: (tz) Update Timezone Data to 2022d In-Reply-To: References: Message-ID: On Wed, 28 Sep 2022 03:40:06 GMT, Yoshiki Sato wrote: > Please review this PR. The change include some code changes in ZoneInfoFile.java and TestZoneInfo310.java since tzdata2022d breaks TestZoneInfo310.java. Some minor comments src/java.base/share/classes/sun/util/calendar/ZoneInfoFile.java line 588: > 586: // will not work for Asia/Gaza and Asia/Hebron which follow > 587: // Palestine DST rules. > 588: // No need of hacking for Plaestine DST rules from tz2022d Should this comment be removed, or at least modified to be better explained? test/jdk/sun/util/calendar/zi/TestZoneInfo310.java line 201: > 199: zid.equals("Asia/Tehran") || // last rule mismatch > 200: zid.equals("Asia/Gaza") || > 201: zid.equals("Asia/Hebron") || It'd be helpful to append `// uses "Palestine" rule`. ------------- PR: https://git.openjdk.org/jdk/pull/10460 From naoto at openjdk.org Fri Sep 30 03:36:15 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 30 Sep 2022 03:36:15 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text In-Reply-To: References: <4-c7dC9feD9vgVdjtLf3rgcmBi6yM2kvYErlwzqvDhQ=.2dce9d38-d3af-4038-8ba9-ce462191ddd1@github.com> Message-ID: On Fri, 30 Sep 2022 00:25:24 GMT, Lance Andersen wrote: > > > Understand, I guess I don't see the difference from moving the tags to the actual test but there could be a subtlety I am missing (wouldn't be the first time ;-) ) > > > > > > The runner has a @library/@build tag to build the test case as a library for the said reason. > > Ok, thanks Naoto You are correct, Lance. Yes, the wrapper can be removed. Sorry for the confusion. ------------- PR: https://git.openjdk.org/jdk/pull/10475 From naoto at openjdk.org Fri Sep 30 04:20:39 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 30 Sep 2022 04:20:39 GMT Subject: RFR: 8294357: (tz) Update Timezone Data to 2022d In-Reply-To: References: Message-ID: On Wed, 28 Sep 2022 03:40:06 GMT, Yoshiki Sato wrote: > Please review this PR. The change include some code changes in ZoneInfoFile.java and TestZoneInfo310.java since tzdata2022d breaks TestZoneInfo310.java. test/jdk/java/util/TimeZone/TimeZoneData/displaynames.txt line 170: > 168: Europe/Vilnius EET EEST > 169: Europe/Warsaw CET CEST > 170: Europe/Zaporozhye EET EEST Do we need to remove those newly linked zone ids from testing? ------------- PR: https://git.openjdk.org/jdk/pull/10460 From ysatowse at openjdk.org Fri Sep 30 04:56:30 2022 From: ysatowse at openjdk.org (Yoshiki Sato) Date: Fri, 30 Sep 2022 04:56:30 GMT Subject: RFR: 8294357: (tz) Update Timezone Data to 2022d In-Reply-To: References: Message-ID: On Fri, 30 Sep 2022 04:17:54 GMT, Naoto Sato wrote: >> Please review this PR. The change include some code changes in ZoneInfoFile.java and TestZoneInfo310.java since tzdata2022d breaks TestZoneInfo310.java. > > test/jdk/java/util/TimeZone/TimeZoneData/displaynames.txt line 170: > >> 168: Europe/Vilnius EET EEST >> 169: Europe/Warsaw CET CEST >> 170: Europe/Zaporozhye EET EEST > > Do we need to remove those newly linked zone ids from testing? This file is not maintained by hand but generated from java/util/TimeZone/TimeZoneData/tools/share/Makefile. These two Ukraine zones are integrated to Europe/Kyiv and removed from tzdata/europe, so the entries disappeared in this file. ------------- PR: https://git.openjdk.org/jdk/pull/10460 From coffeys at openjdk.org Fri Sep 30 05:45:07 2022 From: coffeys at openjdk.org (Sean Coffey) Date: Fri, 30 Sep 2022 05:45:07 GMT Subject: RFR: 8294357: (tz) Update Timezone Data to 2022d In-Reply-To: References: Message-ID: On Wed, 28 Sep 2022 03:40:06 GMT, Yoshiki Sato wrote: > Please review this PR. The change include some code changes in ZoneInfoFile.java and TestZoneInfo310.java since tzdata2022d breaks TestZoneInfo310.java. LGTM ------------- Marked as reviewed by coffeys (Reviewer). PR: https://git.openjdk.org/jdk/pull/10460 From naoto at openjdk.org Fri Sep 30 12:46:17 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 30 Sep 2022 12:46:17 GMT Subject: RFR: 8294357: (tz) Update Timezone Data to 2022d In-Reply-To: References: Message-ID: On Wed, 28 Sep 2022 03:40:06 GMT, Yoshiki Sato wrote: > Please review this PR. The change include some code changes in ZoneInfoFile.java and TestZoneInfo310.java since tzdata2022d breaks TestZoneInfo310.java. Marked as reviewed by naoto (Reviewer). ------------- PR: https://git.openjdk.org/jdk/pull/10460 From naoto at openjdk.org Fri Sep 30 12:46:19 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 30 Sep 2022 12:46:19 GMT Subject: RFR: 8294357: (tz) Update Timezone Data to 2022d In-Reply-To: References: Message-ID: On Fri, 30 Sep 2022 04:54:27 GMT, Yoshiki Sato wrote: >> test/jdk/java/util/TimeZone/TimeZoneData/displaynames.txt line 170: >> >>> 168: Europe/Vilnius EET EEST >>> 169: Europe/Warsaw CET CEST >>> 170: Europe/Zaporozhye EET EEST >> >> Do we need to remove those newly linked zone ids from testing? > > This file is not maintained by hand but generated from java/util/TimeZone/TimeZoneData/tools/share/Makefile. > These two Ukraine zones are integrated to Europe/Kyiv and removed from tzdata/europe, so the entries disappeared in this file. OK. It's a bit odd that the links are removed for the test because they still exist as zone ids, and should have the same name as `Europe/Kyiv`. ------------- PR: https://git.openjdk.org/jdk/pull/10460 From ysatowse at openjdk.org Fri Sep 30 12:49:20 2022 From: ysatowse at openjdk.org (Yoshiki Sato) Date: Fri, 30 Sep 2022 12:49:20 GMT Subject: Integrated: 8294357: (tz) Update Timezone Data to 2022d In-Reply-To: References: Message-ID: On Wed, 28 Sep 2022 03:40:06 GMT, Yoshiki Sato wrote: > Please review this PR. The change include some code changes in ZoneInfoFile.java and TestZoneInfo310.java since tzdata2022d breaks TestZoneInfo310.java. This pull request has now been integrated. Changeset: f0157336 Author: Yoshiki Sato Committer: Naoto Sato URL: https://git.openjdk.org/jdk/commit/f01573368f905f27d26f1d07d9cfd26dcc736a54 Stats: 105 lines in 11 files changed: 31 ins; 55 del; 19 mod 8294357: (tz) Update Timezone Data to 2022d Reviewed-by: naoto, coffeys ------------- PR: https://git.openjdk.org/jdk/pull/10460 From duke at openjdk.org Fri Sep 30 13:52:36 2022 From: duke at openjdk.org (Eivind =?UTF-8?B?QmVyZ3N0w7hs?=) Date: Fri, 30 Sep 2022 13:52:36 GMT Subject: RFR: 8282227: Locale information for nb is not working properly In-Reply-To: References: Message-ID: On Tue, 26 Apr 2022 00:32:48 GMT, Naoto Sato wrote: > This was caused by incorporating CLDR v39, which switched the Norwegian locale inheritance from `no` -> `nb` to `nb` ->`no` and moved the resources from `nb` to `no`, which now contradicts Java's locale fallback. Explicitly inheriting `no` from `nb` will fix the issue. Will this fix make its way back to java 17? ------------- PR: https://git.openjdk.org/jdk/pull/8394 From bpb at openjdk.org Fri Sep 30 14:57:23 2022 From: bpb at openjdk.org (Brian Burkhalter) Date: Fri, 30 Sep 2022 14:57:23 GMT Subject: RFR: 8294307: ISO 4217 Amendment 173 Update In-Reply-To: References: Message-ID: On Thu, 29 Sep 2022 23:19:16 GMT, Justin Lu wrote: > Problem: Amendment number outdated > > Fix: Update amendment number + date in properties file and test case data file Marked as reviewed by bpb (Reviewer). ------------- PR: https://git.openjdk.org/jdk/pull/10499 From duke at openjdk.org Fri Sep 30 16:18:28 2022 From: duke at openjdk.org (=?UTF-8?B?0KHQtdGA0LPQtdC5?= =?UTF-8?B?IA==?= =?UTF-8?B?0KbRi9C/0LDQvdC+0LI=?=) Date: Fri, 30 Sep 2022 16:18:28 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text [v3] In-Reply-To: <7R_FJi6DYp4rE7nHNvpW6LPOsa5L_e7ul1ii1t8QeIA=.a8628f49-e0ce-41ee-8c7e-4e8f7faf983e@github.com> References: <7R_FJi6DYp4rE7nHNvpW6LPOsa5L_e7ul1ii1t8QeIA=.a8628f49-e0ce-41ee-8c7e-4e8f7faf983e@github.com> Message-ID: On Thu, 29 Sep 2022 22:29:43 GMT, Brent Christian wrote: >> Justin Lu has updated the pull request incrementally with one additional commit since the last revision: >> >> Tweak indentation in PaternEntry > > src/java.base/share/classes/java/text/PatternEntry.java line 291: > >> 289: // We re-use these objects in order to improve performance >> 290: private StringBuilder newChars = new StringBuilder(); >> 291: private StringBuilder newExtension = new StringBuilder(); > > Again, in 2022, I don't know that this cache+reuse pattern is needed for performance. Due to some [bootstrapping issues](https://stackoverflow.com/questions/71834059/why-invokedynamic-based-string-concatenation-is-not-available-for-javac-in-java) in `java.base` explicit String concatenation is not translated into invokedynamic, so in practice it's faster to use `StringBuilder.append()` than `str1 + str2`, see e.g. https://github.com/openjdk/jdk/pull/3903 ------------- PR: https://git.openjdk.org/jdk/pull/10475 From naoto at openjdk.org Fri Sep 30 16:30:42 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 30 Sep 2022 16:30:42 GMT Subject: RFR: 8294307: ISO 4217 Amendment 173 Update In-Reply-To: References: Message-ID: On Thu, 29 Sep 2022 23:19:16 GMT, Justin Lu wrote: > Problem: Amendment number outdated > > Fix: Update amendment number + date in properties file and test case data file LGTM ------------- Marked as reviewed by naoto (Reviewer). PR: https://git.openjdk.org/jdk/pull/10499 From bchristi at openjdk.org Fri Sep 30 16:56:20 2022 From: bchristi at openjdk.org (Brent Christian) Date: Fri, 30 Sep 2022 16:56:20 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text [v3] In-Reply-To: References: <7R_FJi6DYp4rE7nHNvpW6LPOsa5L_e7ul1ii1t8QeIA=.a8628f49-e0ce-41ee-8c7e-4e8f7faf983e@github.com> Message-ID: On Fri, 30 Sep 2022 16:14:38 GMT, ?????? ??????? wrote: >> src/java.base/share/classes/java/text/PatternEntry.java line 291: >> >>> 289: // We re-use these objects in order to improve performance >>> 290: private StringBuilder newChars = new StringBuilder(); >>> 291: private StringBuilder newExtension = new StringBuilder(); >> >> Again, in 2022, I don't know that this cache+reuse pattern is needed for performance. > > Due to some [bootstrapping issues](https://stackoverflow.com/questions/71834059/why-invokedynamic-based-string-concatenation-is-not-available-for-javac-in-java) in `java.base` explicit String concatenation is not translated into invokedynamic, so in practice it's faster to use `StringBuilder.append()` than `str1 + str2`, see e.g. https://github.com/openjdk/jdk/pull/3903 Thanks. I was not suggesting that we use string concatenation, but rather just remove the `newChar`/`newExtension` fields, and replace, e.g.: `214 newChars.setLength(0);` with `214 StringBuilder newChars = new StringBuilder();` though I'll admit that I don't have a good sense of whether that's worth doing. ------------- PR: https://git.openjdk.org/jdk/pull/10475 From duke at openjdk.org Fri Sep 30 17:13:26 2022 From: duke at openjdk.org (Justin Lu) Date: Fri, 30 Sep 2022 17:13:26 GMT Subject: Integrated: 8294307: ISO 4217 Amendment 173 Update In-Reply-To: References: Message-ID: On Thu, 29 Sep 2022 23:19:16 GMT, Justin Lu wrote: > Problem: Amendment number outdated > > Fix: Update amendment number + date in properties file and test case data file This pull request has now been integrated. Changeset: 3b1bc217 Author: Justin Lu Committer: Naoto Sato URL: https://git.openjdk.org/jdk/commit/3b1bc21727636cb50cd04d958031832f48fe17e3 Stats: 4 lines in 2 files changed: 0 ins; 0 del; 4 mod 8294307: ISO 4217 Amendment 173 Update Reviewed-by: lancea, bpb, naoto ------------- PR: https://git.openjdk.org/jdk/pull/10499 From rriggs at openjdk.org Fri Sep 30 17:36:24 2022 From: rriggs at openjdk.org (Roger Riggs) Date: Fri, 30 Sep 2022 17:36:24 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text [v3] In-Reply-To: References: <7R_FJi6DYp4rE7nHNvpW6LPOsa5L_e7ul1ii1t8QeIA=.a8628f49-e0ce-41ee-8c7e-4e8f7faf983e@github.com> Message-ID: <_A18rxGSIcrT7YHYxDUF23T4Vt3FWKl0Tm9e8wQmt14=.10babfbc-fd94-4af1-9a6a-01c837a7568e@github.com> On Fri, 30 Sep 2022 16:52:40 GMT, Brent Christian wrote: >> Due to some [bootstrapping issues](https://stackoverflow.com/questions/71834059/why-invokedynamic-based-string-concatenation-is-not-available-for-javac-in-java) in `java.base` explicit String concatenation is not translated into invokedynamic, so in practice it's faster to use `StringBuilder.append()` than `str1 + str2`, see e.g. https://github.com/openjdk/jdk/pull/3903 > > Thanks. I was not suggesting that we use string concatenation, but rather just remove the `newChar`/`newExtension` fields, and replace, e.g.: > `214 newChars.setLength(0);` > with > `214 StringBuilder newChars = new StringBuilder();` > though I'll admit that I don't have a good sense of whether that's worth doing. Memory you don't allocate doesn't need to be GC'd. I'd leave it alone and save the GC overhead. ------------- PR: https://git.openjdk.org/jdk/pull/10475 From duke at openjdk.org Fri Sep 30 20:08:10 2022 From: duke at openjdk.org (Justin Lu) Date: Fri, 30 Sep 2022 20:08:10 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text [v4] In-Reply-To: References: Message-ID: > Problem: Unnecessary instances of StringBuffer within java.text (internal only) > > Fix: StringBuffer Replaced with StringBuilder, and adjusted variable/method names Justin Lu has updated the pull request incrementally with two additional commits since the last revision: - Remove comment typo - Remove test wrapper ------------- Changes: - all: https://git.openjdk.org/jdk/pull/10475/files - new: https://git.openjdk.org/jdk/pull/10475/files/cd966f31..442c2a4e Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=10475&range=03 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=10475&range=02-03 Stats: 45 lines in 3 files changed: 9 ins; 35 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/10475.diff Fetch: git fetch https://git.openjdk.org/jdk pull/10475/head:pull/10475 PR: https://git.openjdk.org/jdk/pull/10475 From naoto at openjdk.org Fri Sep 30 23:53:28 2022 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 30 Sep 2022 23:53:28 GMT Subject: RFR: 8294397: Replace StringBuffer with StringBuilder within java.text [v4] In-Reply-To: References: Message-ID: On Fri, 30 Sep 2022 20:08:10 GMT, Justin Lu wrote: >> Problem: Unnecessary instances of StringBuffer within java.text (internal only) >> >> Fix: StringBuffer Replaced with StringBuilder, and adjusted variable/method names > > Justin Lu has updated the pull request incrementally with two additional commits since the last revision: > > - Remove comment typo > - Remove test wrapper LGTM. Thanks for removing the unnecessary wrapper. ------------- Marked as reviewed by naoto (Reviewer). PR: https://git.openjdk.org/jdk/pull/10475