Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Issue #13050 - fix flaky websocket OnMessageStream tests #13093

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

Open
wants to merge 4 commits into
base: jetty-12.1.x
Choose a base branch
from

Conversation

lachlan-roberts
Copy link
Contributor

closes #13050

@lachlan-roberts lachlan-roberts requested review from olamy and joakime May 5, 2025 06:39
@lachlan-roberts lachlan-roberts self-assigned this May 5, 2025
@lachlan-roberts lachlan-roberts moved this to 👀 In review in Jetty 12.1.0 May 5, 2025
Signed-off-by: Lachlan Roberts <[email protected]>
@lachlan-roberts lachlan-roberts requested a review from sbordet May 5, 2025 13:40
@AfterAll
public static void stopContainer() throws Exception
@AfterEach
public void stopContainer() throws Exception
{
components.stop();
Copy link
Contributor

Choose a reason for hiding this comment

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

You should really use LifeCycle.stop(components) and LifeCycle.stop(container).

If, for some reason, in startContainer() an exception is thrown, the field will be null, and calling stop() will cause an NPE.

Signed-off-by: Lachlan Roberts <[email protected]>
@lachlan-roberts lachlan-roberts requested a review from sbordet May 5, 2025 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 👀 In review
Development

Successfully merging this pull request may close these issues.

3 participants