Skip to content

fix(music): 100k-character prompts/lyrics, 8-min queue; v0.2.82 - #168

Merged
ralyodio merged 1 commit into
masterfrom
fix/music-100k
Nov 9, 2026
Merged

ralyodio merged 1 commit into
masterfrom
fix/music-100k

Conversation

@ralyodio

@ralyodio ralyodio commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

This fixes "Prompt must contain 1 to 1000 characters" from /music.

  • Accepted length: c0mpute.com's /api/v1/music and the gateway's POST /v1/music now accept up to 100,000 characters of prompt and 100,000 of lyrics.
  • Clipping: the gateway clips what it auctions to what ACE-Step actually reads: about 1,000 characters of style (256 caption tokens) and 4,000 of lyrics, stopping at a word or line boundary. This keeps the job spec inside the 64 KiB gossip offer, and a test checks that.
  • Queue: the gateway now waits up to 8 minutes for a free music worker, up from 3. One CPU worker handles one song at a time, about 2.5 minutes each, and in a live test a second request timed out waiting behind the first.

Infernet's side shipped in InfernetProtocol/infernet-protocol#163.

Tests: cargo clippy --workspace --all-targets is clean. The Rust music tests pass 6 of 6, including the new clip test, and bun test for music passes.

Bumps the version to v0.2.82.

🤖 Generated with Claude Code

….2.82

'Prompt must contain 1 to 1000 characters' refused long style briefs and
pasted songs. Accept up to 100k characters of each on c0mpute.com's
/api/v1/music and the gateway's /v1/music; the gateway clips what it
auctions to what ACE-Step reads (256 caption tokens ~1000 chars, 2048 lyric
tokens) at a word/line boundary, which keeps the spec inside the 64 KiB
gossip offer.

The gateway also waits up to 8 min (was 3) for a free music worker: one
CPU worker serializes ~2.5 min songs, and a second request timed out
behind the first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown

ThreatCrush Security Scan

13 finding(s)

HIGH/CRITICAL: 1 | MEDIUM: 8 | LOW: 4

Severity Rule Location
HIGH js-ssrf-outbound-request apps/web/public/sw.js:24
MEDIUM js-unescaped-html-sink apps/web/src/app/blog/[slug]/page.tsx:53
MEDIUM js-unescaped-html-sink apps/web/src/app/layout.tsx:80
MEDIUM sh-remote-script-execution scripts/dev-setup.sh:25
MEDIUM sh-eval-expansion scripts/dev-setup.sh:35
MEDIUM sh-remote-script-execution scripts/install.sh:173
MEDIUM sh-remote-script-execution scripts/install.sh:198
MEDIUM sh-remote-script-execution scripts/install.sh:316
MEDIUM sh-remote-script-execution scripts/install.sh:354
LOW py-ssrf-outbound-request examples/business-strategist-agent/chat.py:37
LOW py-ssrf-outbound-request examples/business-strategist-agent/train.py:54
LOW secret-generic-credential node/crates/c0mpute-core/src/webhook.rs:1165
LOW py-path-traversal node/crates/c0mpute-core/tests/fixtures/fake-infernet-text:29

Snippets are redacted; ThreatCrush never prints matched credential material.

@ralyodio
ralyodio merged commit ffdc488 into master Nov 9, 2026
14 checks passed
ralyodio added a commit that referenced this pull request Nov 9, 2026
v0.2.82 was tagged at #168 (music) before #169 merged, so secure-chat messaging and the hosting release race fix were in no release. Ships them; secure-chat floor >=0.2.83.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant