In the RemoteYjsPartition and YjsPartition, some yjs updates may be processed incorrectly. In some cases, a YJS update will surface a set of tag changes as an update to the bot map itself, instead of as separate tags.
This may occur in cases where a bot gets overwritten with another bot (as may be the case if two separate initialization updates for a bot are applied). Currently, the YJS partitions are not correctly setup to handle this case, and simply ignore the updates.
The result of ignoring these updates is a desync between CasualOS and yjs, which may lead to a variety of issues.
In the
RemoteYjsPartitionandYjsPartition, some yjs updates may be processed incorrectly. In some cases, a YJS update will surface a set of tag changes as an update to the bot map itself, instead of as separate tags.This may occur in cases where a bot gets overwritten with another bot (as may be the case if two separate initialization updates for a bot are applied). Currently, the YJS partitions are not correctly setup to handle this case, and simply ignore the updates.
The result of ignoring these updates is a desync between CasualOS and yjs, which may lead to a variety of issues.