Skip to content

fix(concurrency): stop scheduling new tasks after first failure - #181

Merged
luojiyin1987 merged 1 commit into
masterfrom
fix/concurrency-fail-fast
Sep 1, 2026
Merged

fix(concurrency): stop scheduling new tasks after first failure#181
luojiyin1987 merged 1 commit into
masterfrom
fix/concurrency-fail-fast

Conversation

@luojiyin1987

Copy link
Copy Markdown
Contributor

Summary

  • Stop workers from scheduling new tasks after the first rejection.
  • Allow tasks that already started to finish.
  • Add a deterministic regression test for the failure sequence.

Cause

Promise.all() propagated the rejection. Other workers continued to read the shared task index.

Validation

  • npm run lint
  • npm test -- --runInBand
  • 218 tests passed.
  • git diff --check

Security

  • This change does not include logs or secrets.
  • No redaction was required.

@luojiyin1987
luojiyin1987 merged commit a43bc0c into master Sep 1, 2026
5 checks passed
@luojiyin1987
luojiyin1987 deleted the fix/concurrency-fail-fast branch September 1, 2026 08:58
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.

1 participant