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

Data corruption due to source-of-truth mismatch #952

Open
jcranendonk opened this issue Jan 23, 2019 · 1 comment
Open

Data corruption due to source-of-truth mismatch #952

jcranendonk opened this issue Jan 23, 2019 · 1 comment
Assignees
Labels

Comments

@jcranendonk
Copy link
Contributor

When the client and the server disagree about the value of a ref, and the node has a $timestamp value newer than what the server provides, it is possible to cause cached data to be overwritten with atoms of undefined.

Although setting refs with a $timestamp value on the client is not explicitly supported, we want to avoid corrupting cached data.

More investigation is needed to define reproducible steps to trigger.

@jcranendonk jcranendonk self-assigned this Jan 23, 2019
@ghost
Copy link

ghost commented Feb 29, 2024

We don't understand that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant