🚀 Generic Provider Test Live Yjs

📝 How to Test

• Use the rich text editor - Format text, add images, see live cursors & selections sync instantly
• Change names/colors - See awareness updates in the "Users Online" section
• Add more clients - Test with 3, 4, or more simultaneous connections
• Disconnect a client - See how others react and remove the user from awareness
• Toggle offline/online - Simulate network problems and watch synchronization behavior
• Adjust delay/packet loss/jitter - Test sync resilience under adverse network conditions. Jitter causes out-of-order delivery!
• 💥 Enable data corruption - Use the "Data Corruption" slider to corrupt network packets and test message integrity verification! Choose corruption type: Bit Flip (realistic), Truncate (incomplete), Garbage (worst case), or Insert (protocol errors). All messages are protected with CRC32 checksums - corrupted messages are rejected immediately before decoding. Watch console for "CRC32 checksum mismatch" warnings and automatic re-sync!
• 🧪 Run edge case tests - Click the red test buttons to simulate specific sync failure scenarios:
  • 📦 Batch Lost - Disconnects while updates are pending in batch buffer (tests flush-before-disconnect)
  • 🔢 Sequence Overflow - Sets sequence number to 9,007,199,254,740,981 (near MAX_SAFE_INTEGER) to test overflow handling. In real usage at 1000 msg/sec, this takes ~285 years!
  • 💥 Merge Failure - Simulates Y.mergeUpdates throwing an error during batch processing
  • 🔄 Rapid Connect - Calls connect() 3 times simultaneously to test race condition protection (prevents duplicate message handlers and memory leaks)
  Watch the activity log for detailed test results and recommendations!
• Important: BroadcastChannel is disabled to ensure network simulation works properly. By default, tabs in the same browser sync instantly via BroadcastChannel, bypassing the simulated network. This is disabled here so you can see the real effects of packet loss, delay, and jitter.
• Watch for desync warnings - Hash-based monitoring checks sync health every 5s (orange flash = detected & fixed)
• Refresh the page - Data is only in memory, so it resets (no persistence)