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

Unreadable document created in certain cases #417

Closed
1 of 2 tasks
tmathew0309 opened this issue Apr 11, 2022 — with Huly GitHub · 2 comments
Closed
1 of 2 tasks

Unreadable document created in certain cases #417

tmathew0309 opened this issue Apr 11, 2022 — with Huly GitHub · 2 comments
Assignees
Labels

Comments

Copy link

tmathew0309 commented Apr 11, 2022

Checklist

Describe the bug Getting the following error when reading in a serialized document:

org.graalvm.polyglot.PolyglotException: Uncaught TypeError: Cannot read properties of undefined (reading 'origin')
	at <js>.integrate(yjsBackendBundle.js:19628)
	at <js>.integrateStructs(yjsBackendBundle.js:11897)
	at <js>.:=>(yjsBackendBundle.js:11962)
	at <js>.transact(yjsBackendBundle.js:13628)
	at <js>.readUpdateV2(yjsBackendBundle.js:11950)
	at <js>.applyUpdateV2(yjsBackendBundle.js:12045)
	at <js>.applyUpdate(yjsBackendBundle.js:12059)

Document is now effectively corrupted and the user has lost what they were working on.

To Reproduce We haven't been able to reproduce this error yet but two separate clients have run into it over the course of a week. Will continue trying to narrow down what situations seem to cause it.

Expected behavior Serialized document is always readable

Screenshots If applicable, add screenshots to help explain your problem.

Environment Information

  • Happens on both browser and node. x
  • yjs: 13.5.18

Additional context We use a mostly vanilla setup but our clients and server exchange state vectors every minute to calculate and exchange diffs using encodeStateVectorFromUpdate and diffUpdate. Not sure if that helps narrow down why this kind of issue might arise.

Huly®: YJS-388

@nllevin
Copy link

nllevin commented Jun 7, 2023

Hi @dmonad, we ran into this issue again recently. Curious whether you have any updates or any guesses about how documents end up in this unreadable state?

@dmonad dmonad closed this as completed in 29270b5 Sep 18, 2023
@dmonad
Copy link
Member

dmonad commented Sep 19, 2023

This is fixed in the last release. Please open a new issue if it still persists.

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

3 participants