fix(sockets): delete block edge case

[icecrasher321]

Description

Remove all pending operations related to deleted block from queue so others can run without these retries blocking the queue and triggering connection warning.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Delete a block with and edge that goes into it and out of it. And do other stuff after like adding a new block. Connection warning will trigger until cascading failures are all out of the queue.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• All tests pass locally and in CI (bun run test)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• I have updated version numbers as needed (if needed)
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Security Considerations:

• My changes do not introduce any new security vulnerabilities
• I have considered the security implications of my changes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 16, 2025 4:13am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Jul 16, 2025 4:13am

[greptile-apps]

Greptile Summary

This PR fixes a critical bug in the collaborative editing system where deleting a block could cause connection warnings and cascading failures. The issue occurred because pending operations related to a deleted block would remain in the queue, causing endless retry attempts. The fix introduces proper cleanup mechanisms:

1. Adds cancelOperationsForBlock function to remove all pending operations for a deleted block
2. Enhances socket handlers to properly handle deleted block cases with non-retryable failures
3. Modifies the collaborative workflow hook to clean up operations before block deletion

The changes are well-structured and address a real user-facing issue that could disrupt the collaborative editing experience.

PR Description Notes:

• The PR is missing tests despite the complexity of the changes
• The test description could be more detailed about the expected behavior after the fix

Confidence score: 4/5

1. This PR is safe to merge after adding proper tests
2. The code changes are well-thought-out and handle edge cases properly, but lack of tests reduces confidence
3. Focus review attention on operation-queue/store.ts to verify cleanup logic

_{3 files reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[delve-auditor]

✅ No security or compliance issues detected. Reviewed everything up to f80188a.

Security Overview

• 🔎 Scanned files: 3 changed file(s)

Detected Code Changes

The diff is too large to display a summary of code changes.

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.