The timeout handling only took effect on a direct _remotion_render() call. The high-level execute(operation='render') path goes through _render(), which builds a fresh remotion_inputs dict (edit_decisions, output_path, profile) and dropped remotion_timeout_ms — so callers of the documented operation='render' path never got the timeout passed to the Remotion CLI. Forward it there. Adds a test exercising _render() (not just _remotion_render()) to cover the high-level forwarding path. Refs #217 |
||
|---|---|---|
| .. | ||
| contracts | ||
| eval | ||
| pipelines | ||
| qa | ||
| styles | ||
| tools | ||
| __init__.py | ||