On Wed, 1 May 2024 17:52:13 GMT, Weibing Xiao wrote:
> nroff man page update for jar tool.
> This update is caused by the change of
> https://bugs.openjdk.org/browse/JDK-8318971. While the .md man pages got
> updated in other repos, the corresponding nroff man page was n
On Wed, 1 May 2024 17:52:13 GMT, Weibing Xiao wrote:
> nroff man page update for jar tool.
> This update is caused by the change of
> https://bugs.openjdk.org/browse/JDK-8318971. While the .md man pages got
> updated in other repos, the corresponding nroff man page was n
> nroff man page update for jar tool.
> This update is caused by the change of
> https://bugs.openjdk.org/browse/JDK-8318971. While the .md man pages got
> updated in other repos, the corresponding nroff man page was never updated in
> OpenJDK repos
Weibing Xiao has updated t
nroff man page update for jar tool.
This update is caused by the change of
https://bugs.openjdk.org/browse/JDK-8318971. While the .md man pages got
updated in other repos, the corresponding nroff man page was never updated in
OpenJDK repos
-
Commit messages:
- 8331077 : nroff
On Wed, 1 May 2024 14:54:02 GMT, Weibing Xiao wrote:
> nroff man page update for jar tool.
>
> This update is caused by the change of
> https://bugs.openjdk.org/browse/JDK-8318971. While the .md man pages got
> updated in other repos, the corresponding nroff man page wa
On Wed, 1 May 2024 16:15:12 GMT, Weibing Xiao wrote:
>> nroff man page update for jar tool.
>>
>> This update is caused by the change of
>> https://bugs.openjdk.org/browse/JDK-8318971. While the .md man pages got
>> updated in other repos, the corresponding nr
> nroff man page update for jar tool.
>
> This update is caused by the change of
> https://bugs.openjdk.org/browse/JDK-8318971. While the .md man pages got
> updated in other repos, the corresponding nroff man page was never updated in
> OpenJDK repos
Weibing Xiao ha
> nroff man page update for jar tool.
>
> This update is caused by the change of
> https://bugs.openjdk.org/browse/JDK-8318971. While the .md man pages got
> updated in other repos, the corresponding nroff man page was never updated in
> OpenJDK repos
Weibing Xiao ha
nroff man page update for jar tool.
This update is caused by the change of
https://bugs.openjdk.org/browse/JDK-8318971. While the .md man pages got
updated in other repos, the corresponding nroff man page was never updated in
OpenJDK repos
-
Commit messages:
- 8331077 : nroff
On Wed, 10 Jan 2024 17:42:21 GMT, Weibing Xiao wrote:
> Better Error Handling for Jar Tool When Processing Non-existent Files.
>
> It needs to be backported to JDK22.
This pull request has now been integrated.
Changeset: 3daa936f
Author: Weibing Xiao
Committer: Jaikiran
On Wed, 10 Jan 2024 17:02:03 GMT, Weibing Xiao wrote:
> Better Error Handling for Jar Tool When Processing Non-existent Files.
> It is a clean backport.
This pull request has been closed without being integrated.
-
PR: https://git.openjdk.org/jdk22/pull/55
On Wed, 10 Jan 2024 17:02:03 GMT, Weibing Xiao wrote:
> Better Error Handling for Jar Tool When Processing Non-existent Files.
> It is a clean backport.
Use this PR instead https://github.com/openjdk/jdk22/pull/56.
-
PR Comment: https://git.openjdk.org/jdk22/pull/55#issuec
Better Error Handling for Jar Tool When Processing Non-existent Files.
It needs to be backported to JDK22.
-
Commit messages:
- Backport 8ae309ebacd6947bbad2ef168ca13702e1cba099
Changes: https://git.openjdk.org/jdk22/pull/56/files
Webrev:
Better Error Handling for Jar Tool When Processing Non-existent Files.
It is a clean backport.
-
Commit messages:
- Backport 8ae309ebacd6947bbad2ef168ca13702e1cba099
Changes: https://git.openjdk.org/jdk22/pull/55/files
Webrev: https://webrevs.openjdk.org/?repo=jdk22=55=00
On Wed, 13 Dec 2023 18:16:56 GMT, Weibing Xiao wrote:
> Better Error Handling for Jar Tool Processing of "@File"
>
> This is a new PR for this PR since the original developer left the team. See
> all of the review history at https://github.com/openjdk/jdk/pull
> Better Error Handling for Jar Tool Processing of "@File"
>
> This is a new PR for this PR since the original developer left the team. See
> all of the review history at https://github.com/openjdk/jdk/pull/16423.
>
> Thank you.
Weibing Xiao has updated the pull re
On Tue, 19 Dec 2023 17:24:15 GMT, Weibing Xiao wrote:
>> Better Error Handling for Jar Tool Processing of "@File"
>>
>> This is a new PR for this PR since the original developer left the team. See
>> all of the review history at https://github.com/openjd
> Better Error Handling for Jar Tool Processing of "@File"
>
> This is a new PR for this PR since the original developer left the team. See
> all of the review history at https://github.com/openjdk/jdk/pull/16423.
>
> Thank you.
Weibing Xiao has updated the pull re
> Better Error Handling for Jar Tool Processing of "@File"
>
> This is a new PR for this PR since the original developer left the team. See
> all of the review history at https://github.com/openjdk/jdk/pull/16423.
>
> Thank you.
Weibing Xiao has updated the pull re
Better Error Handling for Jar Tool Processing of "@File"
This is a new PR for this PR since the original developer left the team. See
all of the review history at https://github.com/openjdk/jdk/pull/16423.
Thank you.
-
Commit messages:
- 8318971 : Better Error Handling for Jar
On Fri, 3 Nov 2023 18:11:10 GMT, Weibing Xiao wrote:
> File.mkdirs() occasionally fails to create folders on Windows shared folders.
> It turned out that Windows API FindFirstFileW created the error
> ERROR_NO_MORE_FILES. In some of the cases with a valid file path, this error
> s
On Fri, 3 Nov 2023 18:11:10 GMT, Weibing Xiao wrote:
> File.mkdirs() occasionally fails to create folders on Windows shared folders.
> It turned out that Windows API FindFirstFileW created the error
> ERROR_NO_MORE_FILES. In some of the cases with a valid file path, this error
> s
File.mkdirs() occasionally fails to create folders on Windows shared folders.
It turned out that Windows API FindFirstFileW created the error
ERROR_NO_MORE_FILES. In some of the cases with a valid file path, this error
still returns this error code, which supposedly should not.
Adding this
On Mon, 6 Nov 2023 20:19:25 GMT, Brian Burkhalter wrote:
>> src/java.base/windows/native/libjava/canonicalize_md.c line 142:
>>
>>> 140: || (errval == ERROR_NETWORK_UNREACHABLE)
>>> 141: || (errval == ERROR_NETWORK_ACCESS_DENIED)
>>> 142: || (errval ==
On Tue, 15 Aug 2023 17:30:54 GMT, Weibing Xiao wrote:
> Please refer to JDK-8314063.
>
> The failure scenario is due to the setting of connection timeout. It is
> either too small or not an optimal value for the system. When the client
> tries to connect to the server with
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
update the code
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.org/jdk/pull/15294/
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
format the code
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.org/jdk/pull/15294/
On Thu, 24 Aug 2023 18:45:01 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
update the code according to code review
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.
On Tue, 22 Aug 2023 18:21:17 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
refactoring the code according to the comment
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git
On Tue, 22 Aug 2023 18:21:17 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
format the code
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.org/jdk/pull/15294/
On Mon, 21 Aug 2023 22:10:06 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
On Mon, 21 Aug 2023 22:10:06 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
use original logic to create socket to avoid the compatibility issue
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
-
On Sat, 19 Aug 2023 02:15:06 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
update the code based on the review
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.
On Fri, 18 Aug 2023 13:30:54 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
refactor the code and test cases
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.org/jdk/pu
On Fri, 18 Aug 2023 13:20:50 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
re-write close method
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.org/jdk/pull/15294/
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
update the Connection code
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.org/jdk/pu
On Thu, 17 Aug 2023 21:20:04 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
refactor the code and remove pre-created keystore
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git
On Wed, 16 Aug 2023 22:49:24 GMT, Mark Sheppard wrote:
>> Weibing Xiao has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> update the test code
>
> test/jdk/com/sun/jndi/ldap/LdapSSLHandshakeFailur
On Wed, 16 Aug 2023 23:11:11 GMT, Weibing Xiao wrote:
>> Please refer to JDK-8314063.
>>
>> The failure scenario is due to the setting of connection timeout. It is
>> either too small or not an optimal value for the system. When the client
>> tries to connect to
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
updated the code according to the review
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.
he format of the code got changed consequently.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
update the test code
-
Changes:
- all: https://git.openjdk.org/jdk/pull/15294/files
- new: https://git.openjdk.org/jdk/pull/15294/
Please refer to JDK-8314063.
The failure scenario is due to the setting of connection timeout. It is either
too small or not an optimal value for the system. When the client tries to
connect to the server with LDAPs protocol. It requires the handshake after the
socket is created and connected,
On Thu, 3 Aug 2023 17:32:43 GMT, Weibing Xiao wrote:
> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
> the is an IOException generation when the output stream was flushing the
> buffer.
>
> Please refer to the bug https://bugs.openjdk.org/bro
On Wed, 9 Aug 2023 12:52:35 GMT, Weibing Xiao wrote:
>> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
>> the is an IOException generation when the output stream was flushing the
>> buffer.
>>
>> Please refer to the bug https://bugs.
> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
> the is an IOException generation when the output stream was flushing the
> buffer.
>
> Please refer to the bug https://bugs.openjdk.org/browse/JDK-8313657.
Weibing Xiao has updated the pull reques
On Wed, 9 Aug 2023 00:21:55 GMT, Weibing Xiao wrote:
>> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
>> the is an IOException generation when the output stream was flushing the
>> buffer.
>>
>> Please refer to the bug https://bugs.
> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
> the is an IOException generation when the output stream was flushing the
> buffer.
>
> Please refer to the bug https://bugs.openjdk.org/browse/JDK-8313657.
Weibing Xiao has updated the pull reques
On Fri, 4 Aug 2023 19:09:58 GMT, Weibing Xiao wrote:
>> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
>> the is an IOException generation when the output stream was flushing the
>> buffer.
>>
>> Please refer to the bug https://bugs.
> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
> the is an IOException generation when the output stream was flushing the
> buffer.
>
> Please refer to the bug https://bugs.openjdk.org/browse/JDK-8313657.
Weibing Xiao has updated the pull reques
> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
> the is an IOException generation when the output stream was flushing the
> buffer.
>
> Please refer to the bug https://bugs.openjdk.org/browse/JDK-8313657.
Weibing Xiao has updated the pull reques
On Fri, 4 Aug 2023 18:24:04 GMT, Weibing Xiao wrote:
>> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
>> the is an IOException generation when the output stream was flushing the
>> buffer.
>>
>> Please refer to the bug https://bugs.
> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
> the is an IOException generation when the output stream was flushing the
> buffer.
>
> Please refer to the bug https://bugs.openjdk.org/browse/JDK-8313657.
Weibing Xiao has updated the pull reques
On Thu, 3 Aug 2023 17:59:10 GMT, Alan Bateman wrote:
>> com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
>> the is an IOException generation when the output stream was flushing the
>> buffer.
>>
>> Please refer to the bug
com.sun.jndi.ldap.Connection::leanup does not close the underlying socket if
the is an IOException generation when the output stream was flushing the buffer.
Please refer to the bug https://bugs.openjdk.org/browse/JDK-8313657.
-
Commit messages:
- reformat the code
- remove
On Mon, 28 Nov 2022 16:52:09 GMT, Weibing Xiao wrote:
> fix the illegal characters of directory names in Windows
This pull request has now been integrated.
Changeset: cdf9ed07
Author: Weibing Xiao
Committer: Roger Riggs
URL:
https://git.openjdk.org/jdk/com
fix the illegal characters of directory names in Windows
-
Commit messages:
- fix illegal charater of directory name in Windows
Changes: https://git.openjdk.org/jdk/pull/11393/files
Webrev: https://webrevs.openjdk.org/?repo=jdk=11393=00
Issue:
On Tue, 15 Nov 2022 19:02:30 GMT, Weibing Xiao wrote:
> print warning message for java.io.tmpdir when it is set through the command
> line and the value is not good for creating file folder.
This pull request has now been integrated.
Changeset: 8df3bc4e
Author:Weibing Xiao
Com
> print warning message for java.io.tmpdir when it is set through the command
> line and the value is not good for creating file folder.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
update according to the review co
> print warning message for java.io.tmpdir when it is set through the command
> line and the value is not good for creating file folder.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
updated from the review c
> print warning message for java.io.tmpdir when it is set through the command
> line and the value is not good for creating file folder.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
update according to review c
On Tue, 23 Aug 2022 18:32:30 GMT, Weibing Xiao wrote:
> 8290313: Produce warning when user specified java.io.tmpdir directory doesn't
> exist
This pull request has been closed without being integrated.
-
PR: https://git.openjdk.org/jdk/pull/9989
On Fri, 14 Oct 2022 19:25:54 GMT, Weibing Xiao wrote:
>> 8290313: Produce warning when user specified java.io.tmpdir directory
>> doesn't exist
>
> Weibing Xiao has updated the pull request with a new target base due to a
> merge or a rebase. The pull request no
On Tue, 15 Nov 2022 19:02:30 GMT, Weibing Xiao wrote:
> print warning message for java.io.tmpdir when it is set through the command
> line and the value is not good for creating file folder.
1) Removed the link for CSR.
2) Add a new method in SystemProps.java to check if the warning m
> print warning message for java.io.tmpdir when it is set through the command
> line and the value is not good for creating file folder.
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
the change according to review c
print warning message for java.io.tmpdir when it is set through the command
line and the value is not good for creating file folder.
-
Commit messages:
- remove extra line
- warning message for java.io.tmpdir
Changes: https://git.openjdk.org/jdk/pull/11174/files
Webrev:
On Fri, 14 Oct 2022 19:25:54 GMT, Weibing Xiao wrote:
>> 8290313: Produce warning when user specified java.io.tmpdir directory
>> doesn't exist
>
> Weibing Xiao has updated the pull request with a new target base due to a
> merge or a rebase. The pull request no
On Fri, 14 Oct 2022 19:25:54 GMT, Weibing Xiao wrote:
>> 8290313: Produce warning when user specified java.io.tmpdir directory
>> doesn't exist
>
> Weibing Xiao has updated the pull request with a new target base due to a
> merge or a rebase. The pull request no
> 8290313: Produce warning when user specified java.io.tmpdir directory doesn't
> exist
Weibing Xiao has updated the pull request with a new target base due to a merge
or a rebase. The pull request now contains 11 commits:
- Merge branch 'master' into improve-directory-not-existing
> 8290313: Produce warning when user specified java.io.tmpdir directory doesn't
> exist
Weibing Xiao 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 co
On Tue, 23 Aug 2022 18:32:30 GMT, Weibing Xiao wrote:
> 8290313: Produce warning when user specified java.io.tmpdir directory doesn't
> exist
1) Remove the setting in java.security, not displaying the folder name of
java.io.tmpdir
2) Add the change for NIO
3) Update the testing fi
> 8290313: Produce warning when user specified java.io.tmpdir directory doesn't
> exist
Weibing Xiao has updated the pull request incrementally with one additional
commit since the last revision:
add the change for nio and update the code according to the comments
-
C
On Wed, 24 Aug 2022 04:42:54 GMT, David Schlosnagle wrote:
>> 8290313: Produce warning when user specified java.io.tmpdir directory
>> doesn't exist
>
> src/java.base/share/classes/java/io/File.java line 2180:
>
>> 2178:
>> 2179:
>> 2180: if(!tmpdir.exists() || !tmpdir.canWrite()) {
On Tue, 23 Aug 2022 18:32:30 GMT, Weibing Xiao wrote:
> 8290313: Produce warning when user specified java.io.tmpdir directory doesn't
> exist
CSR https://bugs.openjdk.org/browse/JDK-8293246
-
PR: https://git.openjdk.org/jdk/pull/9989
8290313: Produce warning when user specified java.io.tmpdir directory doesn't
exist
-
Commit messages:
- new approach
- change based on the review
- updating according to the comments
- Merge branch 'master' of https://github.com/openjdk/jdk into
82 matches
Mail list logo
