fix(rest): make async import-job cancellation actually stop the worker (#2824)

[baozhoutao]

Summary

Fixes#2824 — cancelling a running async CSV import had no effect: the job kept writing all rows and finished succeeded.

Root cause: with a synchronous storage driver (better-sqlite3 / wasm fallback), every await in the import row loop resolves as a microtask, so a 50k-row import monopolizes the Node event loop for its whole duration. The cancel route's HTTP handler (and every progress poll) never gets to run, so the in-memory flag that shouldCancel polls is never set.

Three-part fix:

• runImport yields one macrotask (setImmediate) at every progress boundary (every progressEvery rows), so pending I/O — the cancel request, progress polls — gets serviced during a large import. Root-cause fix; also unblocks live progress for the wizard.
• The worker's shouldCancel falls back to reading the durable job row: a cancel accepted by another process (or after a restart dropped the in-memory flag) still stops the worker.
• A late cancel wins the terminal state: the final patch never overwrites the cancel route's durable cancelled with succeeded, and a job cancelled while still pending doesn't start at all.

Testing

• 3 new unit tests (import-runner-cancel.test.ts): mid-loop cancel stops at the next checkpoint with truthful counts; no-cancel path unaffected; yield happens even without shouldCancel.
• 3 new integration tests (import-job-integration.test.ts): mid-flight cancel via the route; out-of-band durable cancel (no in-memory flag); late-cancel terminal-state guard.
• Negative verification: 4 of the 5 new tests fail on pre-fix code.
• Full @objectstack/rest suite green (288 tests), build + DTS clean.
• End-to-end showcase UI run on the rebuilt dist: live progress renders during a 50k import (dead at 0% before), clicking 取消导入 stops the worker mid-run (job cancelled at 17600/50000, row count stable afterwards), and an uncancelled control import still succeeds 50000/50000.

Known remaining (out of scope): the wizard shows 「已导入 0 条」 after cancel instead of the actual partial count — objectui frontend issue (objectui#2393).

Co-Authored-By: Claude noreply@anthropic.com

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
spec	Ready	Preview, Comment	Jul 16, 2026 2:44pm

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/rest.

7 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:

• content/docs/api/error-catalog.mdx(via @objectstack/rest)
• content/docs/api/error-handling-server.mdx(via @objectstack/rest)
• content/docs/api/index.mdx(via @objectstack/rest)
• content/docs/plugins/index.mdx(via @objectstack/rest)
• content/docs/plugins/packages.mdx(via @objectstack/rest)
• content/docs/releases/implementation-status.mdx(via @objectstack/rest)
• content/docs/releases/v12.mdx(via @objectstack/rest)

Advisory only. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs origin/main → pass the list as args.docs.