Cookie is < than last snapshot cookie

[elledienne]

I am testing Replier as I am quite interested in how Replicache works - when actively used, Replier works incredibly well, it's fast and reliable.
I have noticed though, that after some inactivity (hours) which include the laptop going on standby etc, if I trigger any mutation from one of the browsers in which I run Replier, the other instances do not update with the following error:

Is this a Replier issue or a Replicache one?

[aboodman]

Hm. That message by itself isn’t an error (hence info log level). But it is surprising that the other instance doesn’t update. I wonder if the pusher channel has gone to sleep and not restarted. Does refreshing fix it? Another thing to look at is whether the websocket to pusher.com has shutdown and/or restarted. To answer the big picture question, no this isn’t an issue with Replicache, but with this demo. But thanks for the report - will figure out what’s going on here. a (phone)

…

On Mon, Sep 11, 2023 at 7:39 AM Lorenzo De Nobili ***@***.***> wrote: I am testing Replier as I am quite interested in how Replicache works - when actively used, Replier works incredibly well, it's fast and reliable. I have noticed though, that after some inactivity (hours) which include the laptop going on standby etc, if I trigger any mutation from one of the browsers in which I run Replier, the other instances do not update with the following error: [image: image] <https://user-images.githubusercontent.com/3903093/267102278-4a21ff35-3d20-4c62-ba15-c48c25eb26a3.png> Is this a Replier issue or a Replicache one? — Reply to this email directly, view it on GitHub <#157>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAATUBCXRVCD3DE6U4EJEZTXZ5EGHANCNFSM6AAAAAA4TVZ4PI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[elledienne]

@aboodman I believe the socket connection is ok as in the logs I see Pusher : : ["Event recd",{"event":"poke","channel":"default","data":{}}] followed by a pull which returns the following

{
    "lastMutationIDChanges": {},
    "cookie": {"version":20,"partialSync":"PARTIAL_SYNC_COMPLETE","order":275},
    "patch": [{
            "op": "put",
            "key": "issue/24329-0",
            "value": {"title":"Bug: tsconfig file keep being reset while excuting running start","priority":"URGENT","status":"CANCELED","modified":1694502994934,"created":1649565127000,"creator":"CaptainJon","kanbanOrder":"a1","id":"24329-0"}
          }]
  }

Which based on my understanding it means the changes are successfully pulled. The UI though, does not update. A refresh does indeed fix the issue.