Issue Bug Resolved

#110829Extension scanner: a file whose scan fails is counted as checked

Georg Tiefenbrunn 09/29/26, 07:20 updated 11/18/26, 08:20

Description

When the scan request for a single file fails, the backend module counts the file as done and only writes the reason to the browser console. The panel then shows “Checked N of N files” and no hint that a file was not scanned. Its hits, if any, are missing from the result.

Build/Sources/TypeScript/install/module/upgrade/extension-scanner.ts, onrejected of the per-file request: it increments doneFiles, updates the status message and the progress bar and calls console.error(reason).

Affected: 14.3.7 and main.

Steps to reproduce

Currently reproducible with #110828: scan an extension that contains a static first-class callable such as GeneralUtility::underscoredToUpperCamelCase(...). Any other server-side error in the per-file scan action shows the same behaviour.

Expected

The panel marks the file as not scanned and names it, for example “Checked 434 of 435 files, 1 failed”, with the file listed in the result.

Actual

“Checked 435 of 435 files” for an extension where one request answered HTTP 500, no visible error. The failure appears only in the browser console, logged from onrejected.

Reviews 2

History 26

  1. Georg Ringer commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-18T08:20:15+00:00" > 11/18/26, 08:20 </span>

    Applied in changeset commit:9c54a4261066fafcea927f927af3ef4683ae53d7.