-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8260861: TrustStoreDescriptor log the same value #1690
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
8260861: TrustStoreDescriptor log the same value #1690
Conversation
…ame value If the both `jssecacerts` and `cacerts` is not defined, the same log is print twice, talking about the `jssecacerts` instead of `cacerts` the second time.
Hi @davinkevin, 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 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 davinkevin" 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 |
@davinkevin The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
/signed |
Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated! |
OCA has been signed and my name has been added into the OCA listing page: What is the next step to make this contribution eligible to merge ? |
/signed |
You are already a known contributor! |
@davinkevin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
I've made all the tasks required, so I don't know why the process is blocked 😓. |
/issue JDK-8260861 |
@XueleiFan Only the author (@davinkevin) is allowed to issue the |
/issue JDK-8260861 |
@davinkevin The primary solved issue for a PR is set through the PR title. Since the current title does not contain an issue reference, it will now be updated. |
@davinkevin This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 718 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. 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 (@XueleiFan) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@davinkevin |
/sponsor |
@XueleiFan @davinkevin Since your change was applied there have been 718 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 105d3e8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
If both jssecacerts and cacerts are not defined, the same log is printed twice, talking about the jssecacerts instead of cacerts the second time.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/1690/head:pull/1690
$ git checkout pull/1690