Skip to content

8235834: IBM-943 charset encoder needs updating #476

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

psawant19
Copy link
Contributor

@psawant19 psawant19 commented Apr 1, 2024

Backporting JDK-8235834 - IBM-943 charset encoder needs updating.
There are few characters which display garbled values when using IBM943C, so this mapping file needs to be backported to fix the issue.

Reported issue : https://bugs.openjdk.org/browse/JDK-8235834


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • JDK-8235834 needs maintainer approval
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8235834: IBM-943 charset encoder needs updating (Bug - P3 - Approved)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/476/head:pull/476
$ git checkout pull/476

Update a local copy of the PR:
$ git checkout pull/476
$ git pull https://git.openjdk.org/jdk8u-dev.git pull/476/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 476

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/476.diff

Webrev

Link to Webrev Comment

Signed-off-by: Pratiksha.Sawant <Pratiksha.Sawant@ibm.com>
@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Apr 1, 2024
@bridgekeeper
Copy link

bridgekeeper bot commented Apr 1, 2024

Hi @psawant19, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user psawant19" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@psawant19
Copy link
Contributor Author

This contribution is on behalf of my employer, IBM, which is a corporate OCA signatory.

@psawant19
Copy link
Contributor Author

/covered

@openjdk
Copy link

openjdk bot commented Apr 1, 2024

@psawant19 This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8235834: IBM-943 charset encoder needs updating

Apply 34B003AF.RPMAP130 definition into encoder

Reviewed-by: sgehwolf

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@jerboaa) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@bridgekeeper bridgekeeper bot added the oca-verify Needs verification of OCA signatory status label Apr 1, 2024
@bridgekeeper
Copy link

bridgekeeper bot commented Apr 1, 2024

Thank you! Please allow for a few business days to verify that your employer has signed the OCA. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

@psawant19
Copy link
Contributor Author

/covered

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 2, 2024

Already processed the covered command

@psawant19
Copy link
Contributor Author

/covered

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 8, 2024

Already processed the covered command

@psawant19
Copy link
Contributor Author

Closing this PR as my OCA verification is taking too long to approve.
Opened another PR by a different contributor:- #480.

@psawant19 psawant19 closed this Apr 15, 2024
@psawant19 psawant19 reopened this Apr 29, 2024
@bridgekeeper bridgekeeper bot removed oca Needs verification of OCA signatory status oca-verify Needs verification of OCA signatory status labels Apr 29, 2024
@psawant19
Copy link
Contributor Author

/covered

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 29, 2024

You are already a known contributor!

@psawant19
Copy link
Contributor Author

Backporting JDK-8235834 - IBM-943 charset encoder needs updating.
There are few characters which display garbled values when using IBM943C, so this mapping file needs to be backported to fix the issue.

Reported issue : https://bugs.openjdk.org/browse/JDK-8235834.

@psawant19 psawant19 changed the title Backport 1b925183894778acce8aff4c101f67af98f0097f 8235834: IBM-943 charset encoder needs updating Apr 29, 2024
@psawant19 psawant19 changed the title 8235834: IBM-943 charset encoder needs updating Backport 1b925183894778acce8aff4c101f67af98f0097f Apr 29, 2024
@openjdk openjdk bot added the rfr Pull request is ready for review label Apr 29, 2024
@openjdk openjdk bot changed the title Backport 1b925183894778acce8aff4c101f67af98f0097f 8235834: IBM-943 charset encoder needs updating Apr 29, 2024
@openjdk
Copy link

openjdk bot commented Apr 29, 2024

This backport pull request has now been updated with issue and summary from the original commit.

@openjdk openjdk bot added the backport label Apr 29, 2024
@mlbridge
Copy link

mlbridge bot commented Apr 29, 2024

Webrevs

@psawant19
Copy link
Contributor Author

@gnu-andrew, @mrserb Could you please review this PR.

@offamitkumar
Copy link
Member

Hi @psawant19 ,
This PR doesn't make any sense if #480 is in review. Please close one of them.

Copy link
Contributor

@jerboaa jerboaa left a comment

Choose a reason for hiding this comment

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

The test fails:

/disk/openjdk/upstream-sources/git/jdk8u-dev/jdk/test/sun/nio/cs/TestIBMBugs.java:223: error: cannot find symbol
            if (!Arrays.equals(byteIBM943c2b, strIBM943c2b1.getBytes(cs))) {
                 ^
  symbol:   variable Arrays
  location: class TestIBMBugs
1 error
result: Failed. Compilation failed: Compilation failed

Adding the import should fix it.

Also, please enable GHA for your fork and show some evidence on what testing you've done for this. Thanks!

@psawant19
Copy link
Contributor Author

@jerboaa,
I have fixed the compilation error and GHAs are enabled on this repo.
IBM943 mapping document link: https://www.fileformat.info/info/charset/x-IBM943/list.htm

Attaching test evidences for the bug fix with before and after screenshots.

Before fix:
image

After fix:
image

@jerboaa
Copy link
Contributor

jerboaa commented May 16, 2024

@psawant19 Thanks. Please also show that the sun/nio/cs jtreg tests are passing.

Copy link
Contributor

@jerboaa jerboaa left a comment

Choose a reason for hiding this comment

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

This looks OK.

@jerboaa
Copy link
Contributor

jerboaa commented May 16, 2024

I have fixed the compilation error and GHAs are enabled on this repo.

Please merge lastest master into your branch, which should make the certinga CA tests failure go away.

@openjdk
Copy link

openjdk bot commented May 16, 2024

⚠️ @psawant19 This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

@psawant19
Copy link
Contributor Author

@jerboaa,
There is still 1 pre-test failing that is because these below packages doesn't exist at this location.

Is the PR good to go for maintainer approval?

@offamitkumar
Copy link
Member

Is the PR good to go for maintainer approval?

Yes, use /approval request <your reason> to apply for the approval. Please give justification why you want to backport the changes, what testing you have done and what is risk (low/high). In this case it should be low.

@psawant19
Copy link
Contributor Author

/approval request This back port is required to display Japanese locale which uses IBM943 charset.
The fix is tested in a linux environment and the test case passes as mentioned in the screenshot above.

@openjdk
Copy link

openjdk bot commented May 16, 2024

@psawant19
8235834: The approval request has been created successfully.

@openjdk openjdk bot added the approval label May 16, 2024
@jerboaa
Copy link
Contributor

jerboaa commented May 16, 2024

The follow-up, JDK-8239965, needs backporting too. Please do that so that I can approve them as a unit.

@psawant19
Copy link
Contributor Author

This is the PR (#500) created for backporting JDK-8239965.

@openjdk openjdk bot added ready Pull request is ready to be integrated and removed approval labels May 17, 2024
@psawant19
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label May 17, 2024
@openjdk
Copy link

openjdk bot commented May 17, 2024

@psawant19
Your change (at version bde1d37) is now ready to be sponsored by a Committer.

@openjdk
Copy link

openjdk bot commented May 17, 2024

⚠️ @psawant19 the full name on your profile does not match the author name in this pull requests' HEAD commit. If this pull request gets integrated then the author name from this pull requests' HEAD commit will be used for the resulting commit. If you wish to push a new commit with a different author name, then please run the following commands in a local repository of your personal fork:

$ git checkout IBM943-support-backport-1b9251
$ git commit --author='Preferred Full Name <you@example.com>' --allow-empty -m 'Update full name'
$ git push

@jerboaa
Copy link
Contributor

jerboaa commented May 22, 2024

/sponsor

@openjdk
Copy link

openjdk bot commented May 22, 2024

Going to push as commit ab408de.
Since your change was applied there has been 1 commit pushed to the master branch:

  • b3308b1: 8328825: Google CAInterop test failures

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label May 22, 2024
@openjdk openjdk bot closed this May 22, 2024
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels May 22, 2024
@openjdk
Copy link

openjdk bot commented May 22, 2024

@jerboaa @psawant19 Pushed as commit ab408de.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

4 participants