There are max message size limitations to using websockets, but local server and its driver do not use websockets. Since local server is frequently used in test scenarios it can lead to things working in test, but not in production. We should add an artificial limitation to the local server or driver that enforces the max message size
When a client application using Antidote crashes or has incorrect transaction handling, some or even many transactions can stay open. These transactions are never forcefully aborted by Antidote. This can potentially leave many txn-coordinator-fsms running forever.
For a database that should be deployed as a long-running system, this behavior is unacceptable. Transactions, that are not used anym
We previously created our own plugin for our company based on this repository.
I'd like to share some points we noticed when we created it. We deleted it in the end because we no longer need collaborative editing features, though.
This is not an issue, so you can close this “issue” after you read it. I just want to pay you back.
I'm sorry I haven't
Collaborative text editor (like Google Docs or CoderPad) with integrated semi-anonymizing voice chat intended to help reduce bias in technical communication.
In Settings : 'Add a new side account' button
Step #2 in Side account creation