https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41918 --- Comment #18 from Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> --- Created attachment 198260 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=198260&action=edit Bug 41918: (QA follow-up) Degrade gracefully without PROCESS privilege Koha::Reports->running queries information_schema.processlist. A MySQL user without the PROCESS privilege still sees its own threads, but if the privilege check fails entirely (or the engine returns an unexpected error) the previous code would let the DBI exception bubble up and abort the calling report run. Wrap the selectall in eval and on failure log via Koha::Logger and treat the result as empty. This means a misconfigured database degrades to "no enforcement" rather than to "no reports can be run", matching the principle that the duplicate-running guard is a safeguard, not a critical path. The POD now documents this fallback so future readers know the empty resultset has two possible meanings: nothing is currently running, or we could not look. The Koha::Logger->warn ensures the latter is still observable in the configured log destination. Test plan: 1) prove t/db_dependent/Koha/Reports.t still passes. 2) Optional: revoke SELECT on information_schema.processlist for the koha DB user, run a report, observe a warning in the logs and the report still executes (with no duplicate enforcement). -- You are receiving this mail because: You are watching all bug changes.