On 05/10/2021 01:32, Christopher Schultz wrote:
All,
I'm sorry about this release. The VOTE has officially passed, but I fear
I may have to re-roll the release as the Maven artifacts were not signed
properly at the time. I'm trying to decide what to do about it.
I can re-roll the release und
On 05/10/2021 08:12, Mark Thomas wrote:
On 05/10/2021 01:32, Christopher Schultz wrote:
All,
I'm sorry about this release. The VOTE has officially passed, but I
fear I may have to re-roll the release as the Maven artifacts were not
signed properly at the time. I'm trying to decide what to do
On 05/10/2021 08:49, Mark Thomas wrote:
On 05/10/2021 08:12, Mark Thomas wrote:
On 05/10/2021 01:32, Christopher Schultz wrote:
All,
I'm sorry about this release. The VOTE has officially passed, but I
fear I may have to re-roll the release as the Maven artifacts were
not signed properly at t
Mark,
On 10/5/21 03:49, Mark Thomas wrote:
On 05/10/2021 08:12, Mark Thomas wrote:
On 05/10/2021 01:32, Christopher Schultz wrote:
All,
I'm sorry about this release. The VOTE has officially passed, but I
fear I may have to re-roll the release as the Maven artifacts were
not signed properly
On 05/10/2021 14:19, Christopher Schultz wrote:
On 10/5/21 03:49, Mark Thomas wrote:
I believe this is fixed. The Maven repository is now closed and the
staging repository in the original VOTE is available:
https://repository.apache.org/content/repositories/orgapachetomcat-1337
What sorce
вт, 5 окт. 2021 г. в 10:49, Mark Thomas :
>
> On 05/10/2021 08:12, Mark Thomas wrote:
> > On 05/10/2021 01:32, Christopher Schultz wrote:
> >> All,
> >>
> >> I'm sorry about this release. The VOTE has officially passed, but I
> >> fear I may have to re-roll the release as the Maven artifacts were n
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
--- Comment #2 from sutharvis...@gmail.com ---
I'm working on reproducing this behavior. I have a following question.
https://github.com/apache/tomcat/blob/main/java/org/apache/tomcat/util/net/SecureNioChannel.java#L794
This line check for whe
https://bz.apache.org/bugzilla/show_bug.cgi?id=65571
--- Comment #3 from Mark Thomas ---
(In reply to sutharvismay from comment #2)
> Shouldn't we receive
> IOException for closing string and not wrap fail string. As per the stack
> trace we had status is CLOSED.
No. The closing and closed flags
