Joaquín Ossandon

Hey @mitchemmc, I'm doing some validations on my server on every update and this is being a problem, because we validate that keys are always in there. How did you...

@mitchemmc do you encounter race conditions where the missing update never arrives, leaving the document without the key? Fallbacks don't work for me since properties are crucial at all times.

hey @mattc! did you manage to solve this problem? it still removes the key temporarily.. so I am getting some errors. but it is never permanent tho

I have the same issue. Another workaround is using `captureTimeout: 0` so the `set` + `delete` are not stacked together. It's this same issue: https://github.com/yjs/yjs/issues/443 It was resolved, but seems...

Hey @mitgr81! No updates yet. We're using garbage collection on every message or new connection. This has helped a bit, but the memory still slowly increases and hits the max...

> > Hey @mitgr81! No updates yet. > > > > > > We're using garbage collection on every message or new connection. This has helped a bit, but the...

Hey @bigfootjon! Running this repository: https://github.com/cacosandon/django-channels-memory-leak, you'll notice the memory leaks. If you remove the sending of large messages, then the problem disappears unless you open/close connections fast enough to...

Hey! Yes, would love to help. Tried and raised some errors, surely because it's outdated and needs a rebase. Will ping him in the PR!

Hey @zswaff! I know it’s an old issue, but may be you can help me! I am using this recommendation: > To save, use Ypy to encode_state_as_update on the backend...

Amazing @zswaff! I already edited some of the code so all consumers have the same YDoc. I have replaced the `receive` method from `YjsConsumer` with this: ```diff + async def...