Skip to content

can we please stop logging normal log entries as warnings? #1103

@MoralCode

Description

@MoralCode

lots of log statements that get printed on every run regardless seem to be logged at the warning level

ARNING/ForkPoolWorker-1] issues_query -- CQR COMPOSING SQL
[worker-query]    | [2026-03-17 19:54:25,120: WARNING/ForkPoolWorker-1] issues_query -- CQR FETCHING AND STORING ROWS
[worker-callback] | [2026-03-17 19:54:25,130: INFO/ForkPoolWorker-1] Task background_callback_f914073a3a764e6de60685affa0a243fd5fa91bfd6e36ec90dc73758343a8c77[60eac720-e8bc-42e4-a04c-a285c4064baf] succeeded in 0.012296996000259242s: None
[worker-callback] | [2026-03-17 19:54:25,425: INFO/MainProcess] Task background_callback_ed0458e5d315bd30c3225202c39e2c0c9dd6bae0900c82f4f164348275b08ca3[52ec0448-ebb7-4af6-a9f6-0735124d578f] received
[worker-callback] | [2026-03-17 19:54:25,436: WARNING/ForkPoolWorker-1] [('queries.issues_query.issues_query', 'STARTED'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING'), (None, 'PENDING')]
[worker-query]    | [2026-03-17 19:54:25,542: WARNING/ForkPoolWorker-1] issues_query -- CQR UPDATING BOOKKEEPING
[worker-query]    | [2026-03-17 19:54:25,544: WARNING/ForkPoolWorker-1] issues_query -- CQR COMMITTING TRANSACTION
[worker-query]    | [2026-03-17 19:54:25,562: WARNING/ForkPoolWorker-1] issues_query -- CQR SUCCESS
[worker-query]    | [2026-03-17 19:54:25,583: WARNING/ForkPoolWorker-1] issues_query COLLECTION - END
[worker-query]    | [2026-03-17 19:54:25,585: INFO/ForkPoolWorker-1] Task queries.issues_query.issues_query[8799359e-3cb5-4b12-a4c4-1320fe953965] succeeded in 0.6537735389993031s: None
[worker-query]    | [2026-03-17 19:54:25,589: INFO/MainProcess] Task queries.commits_query.commits_query[7b50dee2-41be-4eb5-a83a-f34672617f48] received
[worker-query]    | [2026-03-17 19:54:25,592: WARNING/ForkPoolWorker-1] commits_query COLLECTION - START
[worker-query]    | [2026-03-17 19:54:25,607: WARNING/ForkPoolWorker-1] commits_query COLLECTION - CACHING 57 NEW REPOS
[worker-query]    | [2026-03-17 19:54:25,607: WARNING/ForkPoolWorker-1] commits_query COLLECTION - EXECUTING CACHING QUERY
[worker-query]    | [2026-03-17 19:54:25,607: WARNING/ForkPoolWorker-1] commits_query -- CQR CACHE_QUERY_RESULTS BEGIN
[worker-query]    | [2026-03-17 19:54:25,724: WARNING/ForkPoolWorker-1] commits_query -- CQR EXECUTING QUERY
[worker-query]    | [2026-03-17 19:54:25,780: WARNING/ForkPoolWorker-1] commits_query -- CQR STARTING TRANSACTION
[worker-query]    | [2026-03-17 19:54:25,791: WARNING/ForkPoolWorker-1] commits_query -- CQR COMPOSING SQL
[worker-query]    | [2026-03-17 19:54:25,791: WARNING/ForkPoolWorker-1] commits_query -- CQR FETCHING AND STORING ROWS
[worker-callback] | [2026-03-17 19:54:27,450: WARNING/ForkPoolWorker-1] [('queries.issues_query.issues_query', 'SUCCESS'), ('

Can we log these as INFO instead? itll make it easier to filter them out and hone in on things that are actually problems

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions