FYI but not that it matters much at this point, HTTPCORE-729 affects clients as
well, for example, the PR that bumps Apache Commons VFS from 5.1.5 to 5.2 fails
with this issue.
java.lang.NullPointerException
at
org.apache.hc.core5.http.impl.nio.ServerHttp1IOEventHandlerFactory.createHandler(ServerHttp1IOEventHandlerFactory.java:77)
at
org.apache.hc.core5.reactor.SingleCoreIOReactor.processPendingChannels(SingleCoreIOReactor.java:217)
at
org.apache.hc.core5.reactor.SingleCoreIOReactor.doExecute(SingleCoreIOReactor.java:137)
at
org.apache.hc.core5.reactor.AbstractSingleCoreIOReactor.execute(AbstractSingleCoreIOReactor.java:86)
at
org.apache.hc.core5.reactor.IOReactorWorker.run(IOReactorWorker.java:44)
at java.lang.Thread.run(Thread.java:750)
Gary
On 2022/12/03 11:02:39 Oleg Kalnichevski wrote:
> On Sat, 2022-12-03 at 05:44 -0500, Gary Gregory wrote:
> > Any chance you would release Core first to pick up the NPE fix for
> > HTTPCORE‐729, then have Client pick up Core 5.2.1?
> >
>
> I think HTTPCORE‐729 affects server side protocol handling code only
> and has no impact on HttpClient functionality. I find regressions in
> HttpClient more urgent. I will do HttpCore 5.2.1 immediately after.
>
> Oleg
>
>
> > Gary
> >
> > On Sat, Dec 3, 2022, 04:36 Oleg Kalnichevski <[email protected]>
> > wrote:
> >
> > > Folks
> > >
> > > Please review and amend HttpClient 5.2.1 release notes as you deem
> > > appropriate.
> > >
> > >
> > > https://github.com/apache/httpcomponents-client/blob/master/RELEASE_NOTES.txt
> > >
> > > Oleg
> > >
> > > -------------------------------------------------------------------
> > > --
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
