Exclude some failing tests from
security/infra/java/security/cert/CertPathValidator
-
Commit messages:
- 8263069: Exclude some failing tests from
security/infra/java/security/cert/CertPathValidator
Changes: https://git.openjdk.java.net/jdk/pull/2840/files
Webrev: https://webrevs.
On Thu, 4 Mar 2021 18:19:33 GMT, Vladimir Kempik wrote:
> Hello
> there is one issue with the info you provided, it's from Xcode12.5 beta.
> And beta license agreement forbids sharing output of beta version of
> compiler&co
> So we can't say we have issue with newer xcode beta until that beta we
Hi,
On Fri, Mar 5, 2021 at 2:05 AM Xue-Lei Fan wrote:
> Does it mean that when switch to HTTP/2, the concern is not valid any
> longer? Or there is an alternative solution? Sorry for the questions, I
> know little about servlet. I'm trying to understand the requirement of
> this feature.
>
M
(Moving to security-dev and bcc-ing jdk-dev)
This issue is fixed in JDK 16 [1], and the API is now deprecated [2],
along with several other related APIs that used that term.
--Sean
[1] https://hg.openjdk.java.net/jdk/jdk/rev/145e1859a0a8
[2]
https://download.java.net/java/early_access/jdk16/
Hi,
That looks good! I wanted to mention this for years, and when I finally do,
you already fixed it :)
Kind regards,
Arjan
On Fri, Mar 5, 2021 at 2:52 PM Sean Mullan wrote:
> (Moving to security-dev and bcc-ing jdk-dev)
>
> This issue is fixed in JDK 16 [1], and the API is now deprecated [2
On Thu, 4 Mar 2021 15:56:58 GMT, Fernando Guallini
wrote:
>> Certain JVM tools may access and initialise InetAddress class and its static
>> fields during start up resulting in a NameService implementation being
>> already set to the default **PlatformNameService**, causing intermittent
>> fa
On Thu, 4 Mar 2021 15:56:58 GMT, Fernando Guallini
wrote:
>> Certain JVM tools may access and initialise InetAddress class and its static
>> fields during start up resulting in a NameService implementation being
>> already set to the default **PlatformNameService**, causing intermittent
>> fa
On Thu, 4 Mar 2021 10:35:35 GMT, Daniel Fuchs wrote:
>> Evan Whelan has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> 8262438: Removed custom socket handling logic
>
> I don't see any specific issue with what you are proposing from a netwo
Thanks for the detailed information. I have a better sense of the scenarios
now. What about HTTP/2? Will the business logic or scenarios get changed for
HTTP/2? Could the change apply to HTTP/1.1 as well?
Xuelei
On Mar 5, 2021, at 5:43 AM, arjan tijms
mailto:arjan.ti...@gmail.com>> wrote:
Hi,
On Fri, Mar 5, 2021 at 5:21 PM Xue-Lei Fan wrote:
> Thanks for the detailed information. I have a better sense of the
> scenarios now. What about HTTP/2? Will the business logic
> or scenarios get changed for HTTP/2? Could the change apply to HTTP/1.1 as
> well?
>
For HTTP/2 we'll have t
On Wed, 3 Mar 2021 12:23:00 GMT, Fernando Guallini
wrote:
> Certain JVM tools may access and initialise InetAddress class and its static
> fields during start up resulting in a NameService implementation being
> already set to the default **PlatformNameService**, causing intermittent
> failur
On Mon, 22 Feb 2021 21:31:21 GMT, Xue-Lei Andrew Fan wrote:
>> Actually there's a much easier solution to reduce the number of slow
>> `put()`s without making any behavioral changes.
>> The cache object could store the earliest expire time, and then exit
>> `expungeExpiredEntries()` early when
On Fri, 5 Mar 2021 11:11:44 GMT, Alan Hayward
wrote:
>>> I was building this PR on a new machine, and I now get the following error:
>>>
>>> > /Users/alahay01/java/gerrit_jdk/src/java.desktop/macosx/native/libjsound/PLATFORM_API_MacOSX_MidiUtils.c:258:31:
>>> > error: cast to smaller integer t
On Tue, 2 Mar 2021 21:00:04 GMT, djelinski
wrote:
>> Under certain load, MemoryCache operations take a substantial fraction of
>> the time needed to complete SSL handshakes. This series of patches improves
>> performance characteristics of MemoryCache, at the cost of a functional
>> change: e
On Sat, 13 Feb 2021 03:05:02 GMT, Anthony Scarpino
wrote:
>> Hi,
>>
>> I need a review of these two simple fixes. One just sets the input
>> bytebuffer position to the limit upon completion of decryption. The second
>> calls the CipherCore method to clear the state from the previous operati
15 matches
Mail list logo
