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

backport: Fix the websockets terminate issue #4332

Merged
merged 1 commit into from
Jan 30, 2024

Conversation

chenyukang
Copy link
Collaborator

What problem does this PR solve?

Problem Summary:

There is a trivial issue introduced in #4314, the shutdown layer didn't applied to websocket after the PR, which makes it will hung up when server terminate websocket.

What is changed and how it works?

Fix the shutdown handler, make it's default for HTTP and Websocket, since we will always send exit signal in these two scenario, so we can make the code simpler.

What's Changed:

Related changes

  • PR to update owner/repo:
  • Need to cherry-pick to the release branch

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code ci-runs-only: [ quick_checks,linters ]

Side effects

  • Performance regression
  • Breaking backward compatibility

Release note

Title Only: Include only the PR title in the release note.

@chenyukang chenyukang requested a review from a team as a code owner January 30, 2024 02:53
@chenyukang chenyukang requested a review from quake January 30, 2024 02:53
@quake quake merged commit 337a3bc into nervosnetwork:rc/v0.113.x Jan 30, 2024
31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants