Declare isolated workers in bounded recipe integration

Open Beginner friendly
#2,466 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript, wordpress
Domain
testing

Research direction

Start with tests/bounded-recipe-plan.integration.test.ts and inspect how the WordPress Playground runtime is created for the bounded-plan concurrency-2 case. Run that standalone integration test first, then the full smoke aggregate. Done means both wordpress.run-php entries complete successfully, the fixture declares two workers, and production defaults remain unchanged.

Written by the indexing model from the issue text.

Description

Problem

tests/bounded-recipe-plan.integration.test.ts requests bounded-plan concurrency 2 but creates a WordPress Playground runtime without a worker count. Since #2323, mutable Playground runtimes intentionally default to one request worker. Both concurrent wordpress.run-php entries therefore occupy a one-worker transport and time out after 30 seconds.

This remained hidden because #2459 corrected only the fake-runtime unit concurrency proof. The real recipe integration still omitted the runtime capability it exercises. It failed both in the full aggregate and standalone while verifying #2464.

Desired outcome

Make the integration fixture explicitly request two Playground workers, matching its plan concurrency and per-entry process identities. Preserve the production default of one worker for mutable-state coherence.

Acceptance criteria

  • The real bounded recipe integration executes both entries successfully.
  • The fixture explicitly declares the worker concurrency it requires.
  • Production runtime defaults remain unchanged.
  • The full smoke aggregate passes.

AI assistance

GPT-5.6 Sol via OpenCode traced the integration timeout through the bounded scheduler and Playground request-worker configuration and drafted this tracker under Chris Huber's direction.

Dominant language
TypeScript
Stars
17
Forks
4
Avg merge
53m
Merged PRs (30d)
114

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/wp-codebox

All issues in Automattic/wp-codebox

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.