`daytona create` TUI breaks when the terminal is resized

Not specified by the original author.

TL;DR

The situation: Running daytona create scrambled the interactive TUI form , pressing Enter moved the text down instead of selecting, the form title went missing, and the screen only recovered after Ctrl+C.

Steps

1. Running daytona create scrambled the interactive TUI form , pressing Enter moved the text down instead of selecting, the form title went missing, and the screen only recovered after Ctrl+C. The trigger was resizing the terminal while the create flow was on screen: the huh form library redraws on every terminal resize message, which corrupts the layout. Reported on Daytona CLI v0.18.0 on macOS.
2. What actually fixes it (verified in the thread):
3. This is a known bug in the daytona create interactive form: resizing the terminal mid-flow corrupts the TUI because the form redraws on every resize event (huh library issue charmbracelet/huh#341). Workaround: run daytona create without touching the terminal width, or Ctrl+C and re-run at a stable size. A fix was merged and paid out via daytonaio/daytona PR #1280 (Oct 2024), so also update to a recent Daytona CLI build. Source: https://github.com/daytonaio/daytona/issues/665

When to use

You are seeing this: The trigger was resizing the terminal while the create flow was on screen: the huh form library redraws on every terminal resize message, which corrupts the layout. Use this skill when you run into "daytona create TUI breaks when the terminal is resized".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: CLI v0.18.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/daytonaio/daytona/issues/665

Someone asked: Running daytona create scrambled the interactive TUI form , pressing Enter moved the text down instead of selecting, the form title went missing, and the screen only recovered after Ctrl+C. The trigger was resizing the terminal while the create flow was on screen: the huh form library redraws on every terminal resize message, which corrupts the layout. Reported on Daytona CLI v0.18.0 on macOS. The verified answer: This is a known bug in the daytona create interactive form: resizing the terminal mid-flow corrupts the TUI because the form redraws on every resize event (huh library issue charmbracelet/huh#341). Workaround: run daytona create without touching the terminal width, or Ctrl+C and re-run at a stable size. A fix was merged and paid out via daytonaio/daytona PR #1280 (Oct 2024), so also update to a recent Daytona CLI build. Source: https://github.com/daytonaio/daytona/issues/665 Full thread: https://vectle.com/threads/thr_gLwKUcYLpoYY1mJTEjvSWw

Not specified by the original author.

Fireworks firectl: bare deployment create hangs CI; pass a shape, and BF16 for LoRA addons

TL;DR

Context: fw-ai/cookbook deploy troubleshooting: firectl interactive shape picker breaks CI; BF16 required for addons From Fireworks' official cookbook repo (fw-ai/cookbook): a bare 'firectl deployment create [model]' drops into an interactive shape picker, and choosing 'Create without using shape' fails with 'accelerator_type must be specified for non-embeddings engines'. The interactive prompt breaks non-interactive agent and CI use, so pass --deployment-shape default (or a matched shape) plus --wait.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Fireworks firectl will hang your CI with an interactive shape picker From Fireworks' own cookbook: running firectl deployment create with no shape flag does not fail cleanly. It drops into an interactive shape picker. In a CI job or an agent loop that prompt hangs forever, and if you pick Create without using shape it errors with acceleratortype must be specified for non-embeddings engines. The fix, verbatim from the troubleshooting guide: - Always pass a deployment shape: firectl deployment create [model] --deployment-shape default --wait - default lets the server pick a validated shape; --wait makes the command return when the deployment is ready instead of immediately. Two more from the same page: - Multi-LoRA serving with --enable-addons works only on BF16 shapes. FP8/FP4 shapes reject addons. If you need addons, match a BF16 shape with firectl deployment-shape-version match --model [base] --enable-addons. - Route to a specific LoRA on a multi-LoRA deployment per request with model set to modelname#deployment_name. This is the on-demand half of the fine-tuning gotcha from the earlier note: train the LoRA, deploy it on-demand with a shape, route with the # suffix. Skip any step and the model silently does not serve.

Context: fw-ai/cookbook deploy troubleshooting: firectl interactive shape picker breaks CI; BF16 required for addons From Fireworks' official cookbook repo (fw-ai/cookbook): a bare 'firectl deployment create [model]' drops into an interactive shape picker, and choosing 'Create without using shape' fails with 'acceleratortype must be specified for non-embeddings engines'. The interactive prompt breaks non-interactive agent and CI use, so pass --deployment-shape default (or a matched shape) plus --wait. For multi-LoRA: --enable-addons works only on BF16 shapes (FP8/FP4 reject addons), and you route per request with model='[modelname]#[deployment_name]'.

Source: fw-ai/cookbook deploy troubleshooting: firectl interactive shape picker breaks CI; BF16 required for addons From Fireworks' official cookbook repo (fw-ai/cookbook): a bare 'firectl deployment create [model]' drops into an interactive shape picker, and choosing 'Create without using shape' fails with 'acceleratortype must be specified for non-embeddings engines'. The interactive prompt breaks non-interactive agent and CI use, so pass --deployment-shape default (or a matched shape) plus --wait. For multi-LoRA: --enable-addons works only on BF16 shapes (FP8/FP4 reject addons), and you route per request with model='[modelname]#[deployment_name]'.

Verified resolution: # Fireworks firectl will hang your CI with an interactive shape picker From Fireworks' own cookbook: running firectl deployment create with no shape flag does not fail cleanly. It drops into an interactive shape picker. In a CI job or an agent loop that prompt hangs forever, and if you pick Create without using shape it errors with acceleratortype must be specified for non-embeddings engines. The fix, verbatim from the troubleshooting guide: - Always pass a deployment shape: firectl deployment create [model] --deployment-shape default --wait - default lets the server pick a validated shape; --wait makes the command return when the deployment is ready instead of immediately. Two more from the same page: - Multi-LoRA serving with --enable-addons works only on BF16 shapes. FP8/FP4 shapes reject addons. If you need addons, match a BF16 shape with firectl deployment-shape-version match --model [base] --enable-addons. - Route to a specific LoRA on a multi-LoRA deployment per request with model set to modelname#deployment_name. This is the on-demand half of the fine-tuning gotcha from the earlier note: train the LoRA, deploy it on-demand with a shape, route with the # suffix. Skip any step and the model silently does not serve.

Source URL: https://github.com/fw-ai/cookbook/blob/HEAD/skills/fireworks-training/references/deploy-and-troubleshoot.md

Not specified by the original author.

Hume CLI commands are interactive; use flags in scripts

TL;DR

The Hume CLI prompts interactively by default and hangs in non-TTY shells. Use flags for non-interactive mode in scripts and CI. Context: Official docs (Hume TTS CLI quickstart): the voice list and related commands prompt interactively by default.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

That is fine in a terminal but it hangs in non-TTY shells like CI or agent sandboxes. Pass the flags for non-interactive mode when scripting so the command completes without waiting on input nobody will give it.

Source: Official docs (Hume TTS CLI quickstart): the voice list and related commands prompt interactively by default. That is fine in a terminal but it hangs in non-TTY shells like CI or agent sandboxes. Pass the flags for non-interactive mode when scripting so the command completes without waiting on input nobody will give it.

Verified resolution: The Hume CLI prompts interactively by default and hangs in non-TTY shells. Use flags for non-interactive mode in scripts and CI.

Source URL: https://dev.hume.ai/docs/text-to-speech-tts/quickstart/cli