-
Notifications
You must be signed in to change notification settings - Fork 169
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
Add rtt
to Client
#914
Open
n1ghtmare
wants to merge
1
commit into
nats-io:main
Choose a base branch
from
n1ghtmare:n1ghtmare/rtt-for-client
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add rtt
to Client
#914
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
Jarema
requested changes
Apr 5, 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.
Looks good, except error type.
Jarema
requested changes
Apr 5, 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.
One more change needed.
This does not return RTT, as it does not await PONG.
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
2 times, most recently
from
April 7, 2023 21:38
42a515e
to
2e97188
Compare
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
3 times, most recently
from
April 10, 2023 13:05
de827b8
to
357741e
Compare
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
from
April 10, 2023 17:25
357741e
to
5e0b99d
Compare
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
3 times, most recently
from
April 11, 2023 22:53
33bccae
to
6275f28
Compare
caspervonb
requested changes
Apr 12, 2023
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
from
April 12, 2023 17:04
6275f28
to
428f44e
Compare
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
3 times, most recently
from
April 13, 2023 20:52
b1e5a5d
to
00b98c1
Compare
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
from
May 11, 2023 11:57
00b98c1
to
fbfe019
Compare
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
2 times, most recently
from
May 30, 2023 14:52
97f9721
to
85121a7
Compare
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
from
July 24, 2023 12:42
85121a7
to
c0dfa53
Compare
n1ghtmare
force-pushed
the
n1ghtmare/rtt-for-client
branch
from
July 24, 2023 12:43
c0dfa53
to
c7deee2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes: #909