Skip to content

fix: avoid scaletest prompts without interactive input - #27905

Open
ethanndickson wants to merge 1 commit into
mainfrom
scaletest-runner-6kzn
Open

fix: avoid scaletest prompts without interactive input#27905
ethanndickson wants to merge 1 commit into
mainfrom
scaletest-runner-6kzn

Conversation

@ethanndickson

@ethanndickson ethanndickson commented Aug 6, 2026

Copy link
Copy Markdown
Member

Relates to PRODUCT-534

A user reported that the scaletest runner startup script failed when it invoked coder exp scaletest create-workspaces:

error: prepare build: error creating cancelreader: add reader to epoll interest list
Scaletest failed!

The runner has no interactive stdin, but template parameter resolution tried to open a selector. Bubble Tea then failed whilst creating its Linux cancelreader, so the unresolved template parameter was hidden by this confusing epoll error.

This PR fixes that error message for non-interactive scaletest commands. Instead of trying to prompt, the CLI now identifies the unresolved parameter and tells the user to pass --use-parameter-defaults or set it with --parameter.

The scaletest commands now expose --use-parameter-defaults, and the scaletest runner passes it explicitly when creating workspaces. This lets the runner use declared defaults without attempting to open an interactive selector.

@linear-code

linear-code Bot commented Aug 6, 2026

Copy link
Copy Markdown

PRODUCT-534

@ethanndickson
ethanndickson force-pushed the scaletest-runner-6kzn branch from b206631 to 18a9712 Compare August 6, 2026 03:32
@ethanndickson
ethanndickson marked this pull request as ready for review August 6, 2026 03:34
@coder-tasks

coder-tasks Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Documentation Check

Updates Needed

  • docs/admin/infrastructure/scale-utility.md - The coder exp scaletest create-workspaces example (lines ~56-65) mirrors the scaletest runner's run.sh, which this PR updated to pass --use-parameter-defaults. With the new non-interactive behavior, running this example unattended against a template that has unresolved parameters now errors out instead of prompting. Add --use-parameter-defaults to the documented example to keep it in sync with the runner and reflect the new behavior.

Automated review via Coder Agents

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