Skip to content

maxConcurrency no longer bounds in-flight tests in describe.concurrent, causing per-test resource leaks (regression from v3?) #5657

maxConcurrency no longer bounds in-flight tests in describe.concurrent, causing per-test resource leaks (regression from v3?)

maxConcurrency no longer bounds in-flight tests in describe.concurrent, causing per-test resource leaks (regression from v3?) #5657

Workflow file for this run

name: Issue Labeled
on:
issues:
types: [labeled]
pull_request_target:
types: [labeled]
# for actions-cool/issues-helper to update issues
permissions:
issues: write
pull-requests: write
jobs:
reply-labeled:
runs-on: ubuntu-latest
steps:
- name: needs reproduction
if: github.event.label.name == 'needs reproduction'
uses: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777 # v3.7.6
with:
actions: create-comment
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
body: |
Hello @${{ github.event.issue.user.login }}. Please provide a [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example) using a GitHub repository or [StackBlitz](https://vitest.new) (you can also use [examples](https://github.com/vitest-dev/vitest/tree/main/examples)). Issues marked with `needs reproduction` will be closed if they have no activity within 3 days.
- name: maybe automated (issues)
if: github.event.label.name == 'maybe automated' && github.event_name == 'issues'
uses: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777 # v3.7.6
with:
actions: create-comment
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.issue.number }}
body: |
Hello @${{ github.event.issue.user.login }}. Your issue has been labeled `maybe automated` because it appears to have been fully generated by AI with no human involvement. It will be **closed automatically in 3 days** unless a real person responds.
If you're a real person behind this contribution, please:
- Confirm you've personally reviewed and stand behind its content
- Make sure it follows our [contribution guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md) and uses the correct [GitHub template](https://github.com/vitest-dev/vitest/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml)
- Disclose any AI tools you used (e.g. Claude, Copilot, Codex)
If you believe this was flagged by mistake, leave a comment.
*These measures help us reduce maintenance burden and keep the team's work efficient. See our [AI contributions policy](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md#ai-contributions) for more context.*
- name: maybe automated (pr)
if: github.event.label.name == 'maybe automated' && github.event_name == 'pull_request_target'
uses: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777 # v3.7.6
with:
actions: create-comment
token: ${{ secrets.GITHUB_TOKEN }}
issue-number: ${{ github.event.pull_request.number }}
body: |
Hello @${{ github.event.pull_request.user.login }}. Your PR has been labeled `maybe automated` because it appears to have been fully generated by AI with no human involvement. It will be **closed automatically in 3 days** unless a real person responds.
If you're a real person behind this contribution, please:
- Confirm you've personally reviewed and stand behind its content
- Make sure it follows our [contribution guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md) and uses the correct [GitHub template](https://github.com/vitest-dev/vitest/blob/main/.github/PULL_REQUEST_TEMPLATE.md)
- Disclose any AI tools you used (e.g. Claude, Copilot, Codex)
If you believe this was flagged by mistake, leave a comment.
*These measures help us reduce maintenance burden and keep the team's work efficient. See our [AI contributions policy](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md#ai-contributions) for more context.*