Skip to content

BUG: Log retrieve progress at debug level - #1448

Merged
lassoan merged 1 commit into
commontk:masterfrom
MITK:dicom-retrieve-log-level
Aug 12, 2026
Merged

BUG: Log retrieve progress at debug level#1448
lassoan merged 1 commit into
commontk:masterfrom
MITK:dicom-retrieve-log-level

Conversation

@kislinsk

Copy link
Copy Markdown
Contributor

Disclaimer: We (MITK) are currently catching up on the latest CTK master branch
since we forked for Qt 6 back in 2023. We found a few bugs that are not caught by
your CI and mostly affect external users of CTK.

ctkDICOMQueryRetrieveWidget::updateRetrieveProgress() logs at error
level on every progress tick:

logger.error(QString("setting value to %1").arg(value));

Any application embedding ctkDICOMQueryRetrieveWidget gets its log flooded
during a retrieve. One-line change to logger.debug.

updateRetrieveProgress() is called for every progress tick, so an
error-level trace message floods the log of any application that
embeds ctkDICOMQueryRetrieveWidget.
@lassoan

lassoan commented Jul 25, 2026

Copy link
Copy Markdown
Member

@Punzo is this error-level logging intentional?

@Punzo

Punzo commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

@Punzo is this error-level logging intentional?

@lassoan I don't use this widget in the visual dicom browser and I have not really updated it. In commit 88ff72b I have only updated the widget to use the latest API from the logic classes (ctkDICOMQuery and ctkDICOMRetrieve).

I would agree with @kislinsk that the logger there should be set as debug (or even removed).

@lassoan
lassoan merged commit 868d56c into commontk:master Aug 12, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants