Skip to content

fix: Handle server_notice in audio identification response (#253)#258

Merged
deucebucket merged 1 commit into
developfrom
fix/issue-253-audio-server-notice
Jun 12, 2026
Merged

fix: Handle server_notice in audio identification response (#253)#258
deucebucket merged 1 commit into
developfrom
fix/issue-253-audio-server-notice

Conversation

@deucebucket

Copy link
Copy Markdown
Owner

Summary

  • Added server_notice handling to identify_audio_with_bookdb() in three locations: the initial submit response, the poll completion response, and the final result data
  • Mirrors the existing handling in search_bookdb() (issue [BUG] watch_folder_processed is in-memory only + add handler for Skaldleita server_notice #208): logs notices, respects abort_task action via thread-local _abort_state
  • Previously, BookDB could signal "stop processing" but the audio identification path ignored it, causing unnecessary retries

Closes #253

Test plan

  • python3 test-env/test-naming-issues.py — 290/290 passed
  • ruff check . --select=F821 — all checks passed
  • CI passes
  • Vibe-check bot review

BookDB can return server_notice with action=abort_task to signal LM
should stop processing. This was handled in search_bookdb() but not in
identify_audio_with_bookdb(). Added server_notice handling in three
places: the initial submit response, the poll completion response, and
the final result data (covers old sync path and acts as catch-all).
@deucebucket deucebucket merged commit aa9fca8 into develop Jun 12, 2026
2 of 3 checks passed
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