Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #7683 Use direct buffers for gzip input/output, if configured. #7764

Conversation

jaroslawr
Copy link
Contributor

@jaroslawr jaroslawr commented Mar 21, 2022

Fix for #7683.

return;
_inflater.setInput(compressed);
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(I moved this up because otherwise there is a call done to _inflater.inflate with no input set yet)

@joakime
Copy link
Contributor

joakime commented Mar 21, 2022

@jaroslawr this PR has test failures in both Java 11 and Java 17.

java.util.zip.ZipException: Corrupt GZIP trailer
	at java.base/java.util.zip.GZIPInputStream.readTrailer(GZIPInputStream.java:226)
	at java.base/java.util.zip.GZIPInputStream.read(GZIPInputStream.java:120)
	at [email protected]/org.eclipse.jetty.util.IO.copy(IO.java:166)
	at [email protected]/org.eclipse.jetty.util.IO.copy(IO.java:116)
	at [email protected]/org.eclipse.jetty.servlet.GzipHandlerTest.testAsyncLargeResponse(GzipHandlerTest.java:446)

@jaroslawr jaroslawr force-pushed the jetty-10.0.x-7683-gzip-content-decoder-direct-bufs branch from ee7077c to 0b290c0 Compare March 21, 2022 19:13
@jaroslawr jaroslawr force-pushed the jetty-10.0.x-7683-gzip-content-decoder-direct-bufs branch 2 times, most recently from ab756b9 to dc6fba1 Compare March 22, 2022 14:05
Copy link
Contributor

@lachlan-roberts lachlan-roberts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy with this change.

But I think we should also hear from @sbordet before merging.

@joakime
Copy link
Contributor

joakime commented Mar 23, 2022

The builds are taking much much longer with this latest change.
Old builds: 1 hour 23 minutes (on average).
New builds on this PR: 2 hours (and build is canceled due to overall build timeout)

@jaroslawr
Copy link
Contributor Author

@joakime Builds on other PRs/branches are now also timing out:
https://jenkins.webtide.net/blue/organizations/jenkins/jetty.project/detail/PR-7682/8/pipeline
https://jenkins.webtide.net/blue/organizations/jenkins/jetty.project/detail/jetty-10.0.x/1404/pipeline
So I suppose it's some issue with the CI environment and not with the change itself?

@joakime
Copy link
Contributor

joakime commented Mar 23, 2022

@jaroslawr I see that now too. We are investigating.

@joakime
Copy link
Contributor

joakime commented Mar 24, 2022

Merged (manually) into jetty-10.0.x (and them merged up to jetty-11.0.x)

See: commit a357193

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants