- Notifications
You must be signed in to change notification settings - Fork1.1k
chore(scaletest): avoid polling workspace builds during workspace-updates tests#20534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
chore(scaletest): avoid polling workspace builds during workspace-updates tests#20534
Uh oh!
There was an error while loading.Please reload this page.
Conversation
ethanndickson commentedOct 29, 2025
This stack of pull requests is managed byGraphite. Learn more aboutstacking. |
| typeSlimWorkspacestruct { | ||
| ID uuid.UUID | ||
| Namestring | ||
| } |
ethanndicksonOct 29, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I'm opting to return this new type here instead of thecodersdk.Workspace returned byCreateWorkspace, as I don't want callers ofRunReturningWorkspace to assume that thecodersdk.Workspace being returned contains the latest info about the build.
b90c74a intomainUh oh!
There was an error while loading.Please reload this page.

Uh oh!
There was an error while loading.Please reload this page.
This PR is just committing the changes I made while running the
workspace-updatesload generator.It ensures we're not polling the workspace build progress in the background (while we also watch for workspace updates via the tailnet), and also removes an unnecessary query to
/api/v2/workspace/{id}after each workspace is built.