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

1.0 release #111

Merged
merged 98 commits into from Mar 7, 2017
Merged

1.0 release #111

merged 98 commits into from Mar 7, 2017

Conversation

mattheworiordan
Copy link
Member

Supersedes the working version #99

Complete spec at ably/docs#260

Previously failing in CI because of basic auth credentials in the URL in 1.x and in a header in 2.x
Instead MsgPack & JSON builds will now be run concurrently getting around the max time limit being hit
/app/lib/ably/models/message_encoders/base.rb:10:in `<top (required)>': uninitialized constant Ably::Models (NameError)
When a WS transport becomes disconnected, if the connection state is suspended there is nothing to do
If a method is invoked and it’s failure / success is determined by the client library’s state, then the deferrable errback should always be used i.e. a developer can then reliably always use errback and callback to deal with failure & success respectively.

Exceptions are now only raised when a method is called with invalid arguments.
Normally once the ACK is received the message has been sent to the client. But this is not always the case and in some situations the enter arrived later thus causing the test assertions to fail expecting a later message.
If waitForSync is true, then an error is generated when get is called as the presence map is out of sync at this point.
#RSA5, #RSA6, #TK2a, #TK2b
I incorrectly assumed messages always came before ACKs, but this is no longer the case. This ensures we remove that assumption
@mattheworiordan mattheworiordan merged commit 6013a14 into master Mar 7, 2017
@QuintinWillison QuintinWillison deleted the 1-0-master branch July 23, 2020 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants