Repository navigation
Default task wait 2700s; release sonilo 0.21.1 and sonilo-cli 0.20.1 - #48
Merged
Merged
Conversation
The API now lets a task wait up to 2400s in its upstream provider's queue before giving up, so a 600s client wait abandoned tasks the server was still working on and would bill for if they succeeded. 2700s is that queue ceiling plus margin for generation. The CLI's stems wait keeps its "default wait + 30-minute separation ceiling" sizing (now 4500s, was 2400s), and `video-analysis --timeout` and `tasks wait --timeout` now use the SDK constant instead of a hard-coded 600. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Lightsage docs evalsWaiting for the staging docs URL before running evals. Lightsage will start the selected PR evals automatically when GitHub reports a successful docs deployment for this PR. This usually happens within 15 minutes. Commit: |
…ait) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
steven-panxd
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The API server (sonilo-api-dashboard #420) now lets a task wait up to 2400 seconds in fal's queue before it gives up. Before, the limit was 1200 seconds. On 2026-10-20 fal's sfx-v1.0 app was backlogged: 39 SFX tasks failed at the old 1200-second limit, and the requests that did get a runner waited 850–1160 seconds for it.
The SDK's
DEFAULT_WAIT_TIMEOUTof 600 seconds gives up even earlier than the server ever did. If a client gives up while the server is still waiting and the task later succeeds, the user is billed for a result they never receive. 2700 seconds is the server's 2400-second queue limit plus time for the generation itself.What changed
src/sonilo/resources/tasks.py:DEFAULT_WAIT_TIMEOUTgoes from 600 to 2700, with a comment that ties it to the server's queue limit. Everygenerate()/tasks.wait()that uses the default picks this up.STEMS_WAIT_TIMEOUTwas 2400 (the old 600 default plus the 1800-second separation limit), which would now be shorter than the plain default. It is nowDEFAULT_WAIT_TIMEOUT + 1800= 4500, so it is sized the same way as before.video-analysis --timeoutandtasks wait --timeoutwere hard-coded to 600. They now use the SDK constant, and their help text (andproofread's) prints the constant's value instead of a literal "600".README.md,sonilo-cli/README.md,context7.json, and thetext_to_music/video_to_musicdocstrings.sonilo-cli/tests/test_cli.py: the stems/default timeout assertions now expect 4500 and 2700.Not changed: the per-request HTTP timeout (
_client.DEFAULT_TIMEOUT), the download timeout (types.DOWNLOAD_TIMEOUT), and sonilo-video-kit's own 10-minute ducking wait. No version bump is included; that can go with the next release.Tests
pytest(359 passed),pytest sonilo-video-kit(53 passed), andpytest sonilo-cli(182 passed), run locally on Python 3.12.🤖 Generated with Claude Code