-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[fix][ws] Remove unnecessary ping/pong implementation #20733
Merged
lhotari
merged 2 commits into
apache:master
from
michaeljmarshall:fix-incorrect-ws-ping-pong
Jul 6, 2023
Merged
[fix][ws] Remove unnecessary ping/pong implementation #20733
lhotari
merged 2 commits into
apache:master
from
michaeljmarshall:fix-incorrect-ws-ping-pong
Jul 6, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaeljmarshall
added
type/cleanup
Code or doc cleanups e.g. remove the outdated documentation or remove the code no longer in use
area/websocket
release/2.10.5
release/2.11.2
release/3.0.2
labels
Jul 6, 2023
michaeljmarshall
requested review from
lhotari,
Technoboy-,
eolivelli and
codelipenghui
July 6, 2023 04:48
michaeljmarshall
changed the title
Fix incorrect ws ping pong
[fix][ws] Remove unnecessary ping/pong implementation
Jul 6, 2023
lhotari
approved these changes
Jul 6, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/pulsarbot rerun-failure-checks |
Good work @michaeljmarshall . |
mattisonchao
approved these changes
Jul 6, 2023
nodece
approved these changes
Jul 6, 2023
michaeljmarshall
added a commit
that referenced
this pull request
Jul 6, 2023
(cherry picked from commit 33044f0)
michaeljmarshall
added a commit
that referenced
this pull request
Jul 6, 2023
michaeljmarshall
added a commit
that referenced
this pull request
Jul 6, 2023
(cherry picked from commit 33044f0)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/websocket
cherry-picked/branch-2.10
cherry-picked/branch-2.11
cherry-picked/branch-3.0
doc-not-needed
Your PR changes do not impact docs
release/2.10.5
release/2.11.2
release/3.0.1
type/cleanup
Code or doc cleanups e.g. remove the outdated documentation or remove the code no longer in use
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
This PR removes an incorrect implementation of the websocket proxy ping/pong feature.
The feature was requested here #10014. When it was implemented in #10035, it was added as an endpoint instead of as support for every endpoint, like our
/producer
,/consumer
, and/reader
endpoints. Notably, these endpoint already have support through the framework, so there is no reason for the/pingpong
endpoint. I propose we remove it.Note: since this endpoint should not be used by anyone, I propose we cherry pick this to all active branches.
Modifications
/ws/pingpong
and the/ws/v2/pingpong
endpoints and all associated codeVerifying this change
A test is modified to prove that the framework gives us the ping/pong support out of the box.
Does this pull request potentially affect one of the following parts:
Removes an unnecessary endpoint.
Documentation
doc-not-needed
Ping/pong support is not documented here https://pulsar.apache.org/docs/3.0.x/client-libraries-websocket/, so I think we are good to skip docs.
Matching PR in forked repository
PR in forked repository: michaeljmarshall#52