-
Notifications
You must be signed in to change notification settings - Fork 25
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
RTP17b #835
Merged
Merged
RTP17b #835
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
fff0b4d
RTP17b
ricardopereira da88c56
Test Suite: HTTPURLResponse allHeaderFields is now case-sensitive
ricardopereira ed64c01
Log with error convenience method
ricardopereira ec3a106
RTP17b implementation
ricardopereira 8fb2e0c
Update tests because ARTPresenceMap.isNewestPresence:comparingWith
ricardopereira 3f1bf2d
[fix] Lib is unnecessarily sending another ATTACH
ricardopereira f3933f7
[fix] Check if response body has data
ricardopereira 8dbc03d
Test Suite: fix [ARTPresenceMessage decodeWithEncoder:error:]: unreco…
ricardopereira b50cd73
Channel debug log small improvement
ricardopereira dc84181
syncMsgSerial should only be used when requesting a continue sync
ricardopereira ca32ef2
Remove duplicated remove local member instruction
ricardopereira 1ea0e4c
Presense Message debug log small fix
ricardopereira 0c2d2f5
fixup! RTP17b
ricardopereira ec5a7f0
[fix] Should change the sync state after calling sync method
ricardopereira 68b6967
Remove redundant code
ricardopereira 46dd5e7
fixup! RTP17b
ricardopereira 6058e4a
Merge branch 'develop' into rtp17b
ricardopereira 782ab1e
[fix] Update Logging test which was improved
ricardopereira 0d7cdc0
Sync channelSerial should be unset when the SYNC succeeds.
ricardopereira 9d2ef9e
Test suite: avoid some race conditions
ricardopereira File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
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.
I did this fix in this PR because the RTP17b test was failing because of this. Discussion here.
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.
@ricardopereira With this removal, does the library comply with RTN15c3? "when a resume request results in a CONNECTED with a new connectionId ... The client library should initiate an attach for channels that are in the SUSPENDED state. For all channels in the ATTACHING or ATTACHED state, the client library should fail any previously queued messages for that channel and initiate a new attach..."
cf my comment in slack "you shouldn't be sending an attached after a successful resume, only for an unsuccessful one" -- you still need to do the latter.
(From that test log it looks like the connection moved to
suspended
, but it's not obvious why from the log, the resume was successful so I can't see any reason for it to do so)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.
@SimonWoolf Yes it does. When I implemented
RTN15c3
, I forgot to remove that bit because the new implementation already handle that case. You can see that the channel will reattachably-cocoa/Source/ARTRealtime.m
Lines 608 to 615 in 8dbc03d
ably-cocoa/Source/ARTRealtimeChannel.m
Lines 924 to 934 in 8dbc03d
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.
@SimonWoolf That's because the test forces to suspend:
ably-cocoa/Spec/RealtimeClientPresence.swift
Lines 3034 to 3039 in 8dbc03d
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.
👍
Though looking at
reattachWithReason
, it looks to me like it's reattaching channels in every state except attaching. So (1) it's starting an attach for channels ininitialized
,detached
, orfailed
, which it really shouldn't be; and (2) it isn't initiating a new attach for a channel in theattaching
state (we've just started a completely new connection, so any previously-in-progress attach needs to be started again). Or am I misreading it?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.
@SimonWoolf You're not misreading. It seems so, it's not respecting
RTN15c3
. Issue has been created: #847