Fix CLI-backed Studio actions in bundled runtime (honor PODCLI_BACKEND)#26
Conversation
runCli and the DaVinci export resolved the Python backend at projectRoot/backend, which in a hermetic install points outside the bundle (the launcher ships it under runtime/backend and sets PODCLI_BACKEND). That broke every CLI-backed Studio action there — including the new thumbnail-config import/export/reset, which failed with "can't open .../backend/cli.py: No such file or directory". Resolve the backend dir once (PODCLI_BACKEND, else projectRoot/backend) and use it for runCli, pythonBackend, and the DaVinci CLI, so the same code works in dev and in the bundled runtime on every platform.
|
Warning Review limit reached
More reviews will be available in 32 minutes and 53 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Bug
In the bundled runtime, thumbnail-config import/export/reset failed:
runCli(and the DaVinci export) resolved the Python backend atprojectRoot/backend. In a hermetic install the bundle ships the backend underruntime/backendand the launcher pointsPODCLI_BACKENDat it, so the hardcoded path missed it. This broke every CLI-backed Studio action in the bundle (clips edit, bake-thumbnail, and the new thumbnail-config commands). Executor-based features were unaffected becausepythonBackendalready honoredPODCLI_BACKEND.Fix
Resolve the backend dir once in
paths.ts—PODCLI_BACKENDwhen set, elseprojectRoot/backend— and use it forrunCli,pythonBackend, and the DaVinci CLI path. Works identically in dev and in the bundled runtime, on every platform.Verification
dist/studio/web-server.mjswithPODCLI_BACKENDset (as the launcher does):GET,PUT import, andresetall succeed; no "No such file" errors.npx vitest run— 47 pass (incl.paths.test.ts); root + clienttscclean; studio bundle builds.