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

Partial fix for #12681 caching content #12702

Merged
merged 1 commit into from
Jan 13, 2025
Merged

Conversation

gregw
Copy link
Contributor

@gregw gregw commented Jan 12, 2025

This is a partial fix for #12681. It does not fix the actual release race on a single content, but by restricting the shrinking to a single thread, make the race less likely to occur.

There is a more comprehensive fix in #12678 for 12.1, but the cache has changed too much for a straight forward back port.

This is a partial fix for #12681. It does not fix the actual release race on a single content, but by restricting the shrinking to a single thread, make the race less likely to occur.

There is a more comprehensive fix in #12678 for 12.1, but the cache has changed too much for a straight forward back port.
@gregw gregw requested a review from lorban January 12, 2025 22:17
@gregw
Copy link
Contributor Author

gregw commented Jan 13, 2025

The CI failures look to be a problem with CI configuration for some JVMs. will merge anyway.

@gregw gregw merged commit 73e6058 into jetty-12.0.x Jan 13, 2025
7 of 9 checks passed
@gregw gregw deleted the fix/12681/cachingContent branch January 13, 2025 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

2 participants