Silent coercion of negative `static_delay_ms` to positive is undocumented

Open
#258 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
audio-video-rtc

Research direction

Start with docs/static-delay.md §divergence and the linked per-SDK digest to understand the audit finding, then locate the Python handling of static_delay_ms. Done means the unsupported negative and out-of-range cases have an explicitly chosen behavior, with the relevant documentation and tests updated.

Written by the indexing model from the issue text.

Description

Severity: ⚪ latent

Negative values are silently coerced positive without a warning, and out-of-range values from a misbehaving server are accepted. Either reject explicitly with an error or log on coercion. Spec says negative values are not supported and should never be required for any compliant implementation.

Source: docs/static-delay.md §divergence
Full audit branch: claude/stream-sync-correction-sdks-AWoNC
Per-SDK digest: sdk-issues digest

Filed from a cross-SDK conformance audit; see digest for the full per-SDK punch list.

Dominant language
Python
Stars
190
Forks
36
Avg merge
11d 19h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Sendspin/sendspin-python-cli

All issues in Sendspin/sendspin-python-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.