Skip to content

Feature/1291 concurrent cancel - #1340

Merged
K1NGD4VID merged 5 commits into
LabsCrypt:mainfrom
meem08:feature/1291-concurrent-cancel
Sep 3, 2026
Merged

Feature/1291 concurrent cancel#1340
K1NGD4VID merged 5 commits into
LabsCrypt:mainfrom
meem08:feature/1291-concurrent-cancel

Conversation

@meem08

@meem08 meem08 commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Description

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🔧 Refactoring (no functional changes)
  • ⚡ Performance improvement
  • 🧪 Test addition or update

Related Issues

Closes #1291

Changes Made

Testing

Test Coverage

  • Unit tests added/updated
  • Integration tests added/updated
  • Manual testing performed

Test Steps

Breaking Changes

Breaking Changes:

Migration Guide:

Screenshots/Demo

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • Updated Postman/Hoppscotch API collections if routes changed
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published
  • I have checked for breaking changes and documented them if applicable

Additional Notes

@meem08

meem08 commented Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

@blurbeast review and merge

@meem08
meem08 force-pushed the feature/1291-concurrent-cancel branch from 6274066 to 48ddc45 Compare September 1, 2026 15:10
meem08 and others added 3 commits September 3, 2026 07:28
…anch

- Restore ci.yml, package.json, and package-lock.json to match main: keep
  the changes job, the frontend rollup native binding step, and a lockfile
  in sync so npm ci and the frontend lint environment match main.
- Fix the concurrent-cancel integration test: run it inside the describe
  block with persistent mocks and assert the actual controller behavior
  (each request performs its own on-chain cancel).
- Restore the preserve-manual-memoization suppression and the getAllByText
  assertion in the stream details page/test to match main.

Generated with Codebuff 🤖
Co-Authored-By: Codebuff <noreply@codebuff.com>
… only)

The main merge re-introduced the same breakage as before: package.json became
invalid JSON (duplicate mysql2 override missing a comma, which broke npm ci /
npm audit in every job), the lockfile was churned by a local npm install, and
stream-details-content.tsx got a duplicate liveClaimable const. Restore all
three to match main so the PR's only change is the concurrent-cancel
integration test (LabsCrypt#1291).

Generated with Codebuff 🤖
Co-Authored-By: Codebuff <noreply@codebuff.com>
@K1NGD4VID
K1NGD4VID merged commit 53f4160 into LabsCrypt:main Sep 3, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Audit] No test covers concurrent cancel requests for the same stream

2 participants