Repository navigation
Closed
Labels
bugSomething isn't workingSomething isn't workingtriage/needs-triageNeeds current-behavior, related-work, and scope evaluation.Needs current-behavior, related-work, and scope evaluation.
Description
Describe the bug
The CLI normally allows only one local render per user account; others wait. But Studio calls the renderer directly without acquiring that shared lock. each render sizes its workers against the whole machine, independently of other renders.
Minimal reproduction
hyperframes/packages/cli/src/commands/render/renderSlot.ts
Lines 14 to 22 in 0ca2b1a
| export async function acquireRenderSlot( | |
| plan: Pick<RenderPlan, "project" | "waitForRenderSlot">, | |
| signal?: AbortSignal, | |
| lock: Partial<RenderLockOptions> = {}, | |
| ): Promise<() => void> { | |
| try { | |
| return await acquireRenderLock({ | |
| project: plan.project.dir, | |
| wait: plan.waitForRenderSlot, |
hyperframes/packages/cli/src/server/studioServer.ts
Lines 674 to 681 in 0ca2b1a
| state.progress = j.progress; | |
| if (j.currentStage) state.stage = j.currentStage; | |
| }; | |
| await executeRenderJob( | |
| job, | |
| opts.project.dir, | |
| opts.outputPath, | |
| onProgress, |
Steps to reproduce
Clicking the render button
Expected behavior
Other renders are locked
Actual behavior
All renders are open
Environment
I don't know if I can run this. It is hyperframes studio on Windows 11Additional context
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingtriage/needs-triageNeeds current-behavior, related-work, and scope evaluation.Needs current-behavior, related-work, and scope evaluation.
Activity