-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8328957: Update PKCS11Test.java to not use hardcoded path #18488
Conversation
👋 Welcome back mdonovan! A progress list of the required criteria for merging this PR into |
@mpdonova 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 84 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @mpdonova ,
Thanks for contributing this fix. I've seen in java.nio.file.Files::find doc an implementation note saying that it should be used in a try-with-resource fashion to close the stream and any open directories. Should we consider this?
One more question. The ".orElse(path).getParent()" code path, what case is it intended for? I wonder in which cases this is expected to succeed.
Martin.-
I think adding the try-with-resources is a good idea. Always better to close things that potentially leave them open. The I think this is a cleaner way to do it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I verified that it fixes the problem when running PKCS11 tests with system libraries (e.g. /usr/lib64).
/integrate |
Going to push as commit 16576b8.
Your commit was automatically rebased without conflicts. |
When resolving the location of the NSS library, the code appended a hard-coded path:
/nss/lib
. This makes it difficult for a person to specify the library when it is installed in a location such as/usr/lib64
.In this PR, I removed the hard-coded path and updated the code to search the specified path for the nss library file, softokn3.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18488/head:pull/18488
$ git checkout pull/18488
Update a local copy of the PR:
$ git checkout pull/18488
$ git pull https://git.openjdk.org/jdk.git pull/18488/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18488
View PR using the GUI difftool:
$ git pr show -t 18488
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18488.diff
Webrev
Link to Webrev Comment