On Mon, 7 Feb 2022 13:34:24 GMT, Claes Redestad wrote:
> Looks reasonable.
Thanks. Any more reviews needed, or I am pushing?
-
PR: https://git.openjdk.java.net/jdk/pull/7333
On Thu, 3 Feb 2022 23:29:54 GMT, Naoto Sato wrote:
> Following the prior discussion [1], here is the PR for the subject
> enhancement. CSR has also been updated according to the suggestion.
>
> [1]
> https://mail.openjdk.java.net/pipermail/core-libs-dev/2022-January/085175.html
src/java.base/
On Thu, 3 Feb 2022 23:29:54 GMT, Naoto Sato wrote:
> Following the prior discussion [1], here is the PR for the subject
> enhancement. CSR has also been updated according to the suggestion.
>
> [1]
> https://mail.openjdk.java.net/pipermail/core-libs-dev/2022-January/085175.html
src/java.base/
On Mon, 7 Feb 2022 20:16:43 GMT, Lance Andersen wrote:
>> If you are pretty sure the only other case are as above, I wonder if a
>> simpler fix would be to change `verifiableEntry()` to check for these null
>> cases and throw a `ZipException` which will get directly propagated by
>> `getInputS
> Hi all,
>
> Please review the attached patch to address
>
> - That JarFile::getInputStream did not check for a null ZipEntry passed as a
> parameter
> - Have Zip/JarFile::getInputStream throw a ZipException in the event that an
> unexpected exception occurs
>
> Mach5 tiers1-3 runs are clean
On Mon, 7 Feb 2022 18:44:10 GMT, Sean Mullan wrote:
>> Looking at this a bit more, it looks like `JariFile::initializeVerifier` is
>> the only place currently in `JarFile` that could throw a `JarException` and
>> that method could be called from `JarFile::getInputStream`
>>
>> As `verifiableE
Hi,
I'm not sure where you ended up in this succession of messages. I do think there are
some things going on that are worthy of discussion and possibly fixing. Let me try
to break them down.
1) With the default load factor of 0.75, it's possible to have 12 entries in a map
whose table lengt
On Mon, 7 Feb 2022 16:52:07 GMT, Lance Andersen wrote:
>> `JarException` is a subclass of `ZipException` though, so I think this would
>> be ok to throw and still be compliant with the specification.
>
> Looking at this a bit more, it looks like `JariFile::initializeVerifier` is
> the only pla
On Mon, 7 Feb 2022 15:16:43 GMT, Sean Mullan wrote:
>> JarFile::getInputStream. mentions ZipException but not JarException which is
>> why I chose this. If we change this to JarException, I would need to update
>> the javadoc and create a CSR.
>>
>> Please let me know your preference
>
> `Jar
On Fri, 4 Feb 2022 15:19:11 GMT, Lance Andersen wrote:
>> src/java.base/share/classes/java/util/jar/JarFile.java line 866:
>>
>>> 864: } catch (Exception e2) {
>>> 865: // Any other Exception should be a ZipException
>>> 866: throw (ZipException) new ZipException(
On Thu, 3 Feb 2022 07:20:28 GMT, Aleksey Shipilev wrote:
> I was looking for easy things to do to improve `java.lang.invoke` cold
> performance. One of the things is inlining `VarForm.getMemberName` a bit, so
> that interpreter does not have to call through `getMemberNameOrNull`.
>
> There is
On Fri, 4 Feb 2022 15:36:35 GMT, Aleksei Efimov wrote:
> Hi,
>
> JNDI's `DnsClient` can fail with `UncheckedIOException` during `connect` or
> `disconnect` method calls. It is a [know
> behavior](https://bugs.openjdk.java.net/browse/JDK-8236076) of
> `DatagramSocket`.
>
> Currently, `DnsClie
12 matches
Mail list logo
