deepstreamIO / deepstream.io

deepstream.io server
https://deepstreamio.github.io
MIT License
7.14k stars 381 forks source link

non-existant record #983

Closed thorsby closed 5 years ago

thorsby commented 5 years ago

I have a fresh (version 4.0.6) version of server on Mac/10.12.6 I'm running the quick start tutorial on the deepstream.io website: https://deepstream.io/tutorials/getting-started/javascript/index.html

When the client connects, I get the following on server:

INCOMING_CONNECTION | from undefined (127.0.0.1)
AUTH_SUCCESSFUL | open
VERSION_EXISTS | open tried to update record some-name to version 0 but it already was 0

So already on connect, there is a warning. As soon as I try typing in the HTML input field, I get errors on the server:

RECORD_UPDATE_ERROR | Received update for non-existant record some-name

I tried replacing the server binary with a version running in NodeJS and swapping between client from CDN and NPM.

This example is very simple and pretty coherent with the documentation on records. What am I missing? Is something broken?

yasserf commented 5 years ago

Hello! This was sadly a small regression in a recent release. A fix will be released in the next day or two.

thorsby commented 5 years ago

Okay, thank you. I got it working now with current server@4.0.6, but had to backstep client to 4.0.2.

ilteblick commented 5 years ago

@thorsby Check this link pls https://deepstream.io/tutorials/upgrade-guides/v4/client/index.html. When i use await client.login() problem was resolved.

yasserf commented 5 years ago

Yup! The issue is when you request a record before being logged in with offline disabled. There’s a lot of permutations, trying to find a way to simplify it a bit

yasserf commented 5 years ago

Released 4.0.5 which should address this, please let me know if otherwise!

yasserf commented 5 years ago

Was a client issue, hence the version number :D

thorsby commented 5 years ago

Was a client issue, hence the version number :D

Nice comment, actually clarified 👍 I did not initial realise that client and server was not on same schedule.