Andrew Bulat

Need an example on how to reproduce. Might not be relevant anymore for latest ably-js versions

Just a heads up: > test/ably/rest/resthttp_test.py::TestRestHttp::test_request_headers - test consistently fails after changes, should investigate This is not related to this PR, fixed in https://github.com/ably/ably-python/pull/593. You can ignore `test_request_headers` test failures...

This is related to https://github.com/ably/ably-js/issues/1330 and transport 'no upgrade' work that has been done for ably-js v2 in https://github.com/ably/ably-js/pull/1645

So there already exists [content/getting-started/react.textile](https://github.com/ably/docs/blob/main/content/getting-started/react.textile) file which renders at https://ably.com/docs/getting-started/react. I couldn't straight up replace it with the new content as there are a bunch of places in the docs...

I also removed notes about `AblyProvider` and `ChannelProvider` being updated/added in ably-js 2.0 that are currently visible on https://ably.com/docs/getting-started/react: ably-js 2.0 has been out for a ~year now, I don't...

@m-hulbert went back to using Tailwind in https://github.com/ably/docs/pull/2534/commits/33835a10351fc9a854f777ba606dba7c9aba2b1f. There is last [outstanding question](https://github.com/ably/docs/pull/2534#issuecomment-2804231155) regarding existing [content/getting-started/react.textile](https://github.com/ably/docs/blob/main/content/getting-started/react.textile) file

@coderabbitai review

ok, upon further investigation it seems that even though `cipher.decrypt` might not be a problem here, the `vcdiff` decoding depends on the previous recevied payload in enable to be able...

@owenpearson ^

Hi @bastiankistner ! Thank you for spotting the issue and opening a PR. It LGTM, and we're going to merge it once tests are passing (there is a sandbox issue...