Skip to content

fix: Handle server_notice in audio identification response #253

Description

@deucebucket

Problem

BookDB can return server_notice with action: abort_task in API responses to signal LM should stop sending requests. This is currently handled in search_bookdb() (metadata lookups) but NOT in identify_audio_with_bookdb() (audio identification).

If BookDB wants to tell LM "stop sending audio jobs," it has no way to communicate that through the audio endpoint.

Fix

In library_manager/providers/bookdb.py, add server_notice handling to identify_audio_with_bookdb() — check the response for server_notice field and store it in thread-local _abort_state the same way search_bookdb() does.

Files

  • library_manager/providers/bookdb.py — add server_notice check after audio ID response parsing

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingintegrationCross-system integration

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions