Skip to content

Guard CD-R eject and peak/quality crashes (#619, #601, #621) - #705

Open
ajzrva-sys wants to merge 1 commit into
whipper-team:developfrom
ajzrva-sys:feature/issue-619-621-601-guardrails
Open

ajzrva-sys wants to merge 1 commit into
whipper-team:developfrom
ajzrva-sys:feature/issue-619-621-601-guardrails

Conversation

@ajzrva-sys

@ajzrva-sys ajzrva-sys commented Sep 18, 2026 •

Copy link
Copy Markdown

Refusing a CD-R or an unknown disc skips the requested eject policy. This applies --eject always and --eject failure to those exits too.

Missing peak or quality values can also crash reporting. They now print as unknown. The log accepts a missing peak, and quality/speed calculations handle unread frames and zero elapsed time.

Addresses #619, #601 and #621. Related to #694.

Checked 6a174b2 on macOS arm64 / Python 3.11: 124 unit tests pass. No optical-drive test in this run.

…team#601, whipper-team#621)

- CD-R / unknown-metadata refusal paths now honour --eject always/failure
  (issue whipper-team#619)
- Peak level and rip quality prints tolerate None after soxi or rip-task
  failures (issue whipper-team#601)
- ReadTrackTask does not ZeroDivision-crash on zero duration or unreadable
  frames when computing speed/quality (issue whipper-team#621)
- WhipperLogger writes Peak level safely when peak is None (complements
  open PR whipper-team#694)

Signed-off-by: ajzrva-sys <ajzrva-sys@users.noreply.github.com>
Addresses whipper-team#619, whipper-team#601, whipper-team#621
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