Skip to content
This repository was archived by the owner on Jun 16, 2026. It is now read-only.
This repository was archived by the owner on Jun 16, 2026. It is now read-only.

question about logging #172

Description

@tlambert03

When I instantiate an acquire.Runtime I get a bunch of logging.ERROR level logs for drivers that I'm unlikely to ever use (since I don't have all those cameras).

Log: warn enabled
Log: error enabled
/Users/runner/work/acquire-python/acquire-python/acquire-common/acquire-core-libs/src/acquire-device-hal/device/hal/loader.c:125 - driver_load(): Failed to initialize driver at "acquire-driver-hdcam"
/Users/runner/work/acquire-python/acquire-python/acquire-common/acquire-core-libs/src/acquire-device-hal/device/hal/loader.c:125 - driver_load(): Failed to initialize driver at "acquire-driver-egrabber"
/Users/runner/work/acquire-python/acquire-python/acquire-common/acquire-core-libs/src/acquire-device-hal/device/hal/loader.c:125 - driver_load(): Failed to initialize driver at "acquire-driver-spinnaker"
/Users/runner/work/acquire-python/acquire-python/acquire-common/acquire-core-libs/src/acquire-device-hal/device/hal/loader.c:125 - driver_load(): Failed to initialize driver at "acquire-driver-pvcam"

I can silence these of course with getLogger("acquire").setLevel("CRITICAL") ... but that seems somewhat drastic. Are these just for the time being, intended for eventual removal? Or is there a better way to silence errors on unused drivers?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status
    Priority Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions