Review main Ready for review

97526[FEATURE] Load status report providers asynchronously

Georg Ringer CR 0 V 0 Hard +718 −133 updated 11/20/26, 19:55

Commit message

The status report module renders immediately with a loading
indicator per status provider group. The providers of each group
are executed by one AJAX request, at most four at the same time,
and their merged statuses are shown as soon as they arrive.
JavaScript modules registered by the providers are passed to the
module and loaded after the statuses have been inserted.

The highest severity is remembered per provider and combined into
the overall value used for the system status notification after
each group has been processed. A failing provider is reported with
an error status.

Test this change

Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch

Check out patch set 4
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/26/97526/4 && git checkout FETCH_HEAD
Cherry-pick onto main
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/26/97526/4 && git cherry-pick FETCH_HEAD

Review

  • Code review CR 0 Needs a vote
  • Verified V 0 Needs a vote
    • core-ci +1 CI

Merge conflicts 4

Issues 1

Files 16

Review log 1519

  1. Georg Ringer uploaded patch set 1 11/10/26, 21:37

  2. core-ci voted on patch set 1 V +1 11/10/26, 21:45 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/113989

  3. Georg Ringer commented on patch set 1 11/11/26, 08:49

    This change is ready for review.
  4. Oli Bartsch uploaded patch set 2 V +1 11/11/26, 09:11

  5. Oli Bartsch commented on patch set 2 11/11/26, 09:13

    @georg.ringer@gmail.com The status report now sends one AJAX request per provider group label instead of one per provider class. Providers that share a label are merged and sorted together again, and the overall highest severity is stored at the end of each request, so the client-driven finalize route is gone. The provider endpoint now returns JSON with the HTML and the JavaScript items the providers registered. The module processes those items and fires a `typo3:reports:status-provider-loaded` DOM event once the markup is in the page. A provider that throws now shows up as an ERROR status and is counted as such, and a failed request shows an error callout. The install tool's "disable" link now points to the status module via UriBuilder, and adminCmd is passed on to the provider requests. The registry key is hashed, the dead collectAndStoreSystemStatus() is removed, the changelog documents the changed request context, assets, event and template variables. One open point: concurrent group requests may briefly store a slightly stale overall severity because Registry caches its values per request.
  6. core-ci voted on patch set 2 V +1 11/11/26, 09:20 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114026

  7. Oli Bartsch voted on patch set 2 CR +1 V +1 11/11/26, 09:59

  8. Josef Glatz commented on patch set 2 V +1 11/12/26, 14:00

    tested against some personal existing reports stuff in my playground. all fine.
  9. Andreas Kienast commented on patch set 2 11/12/26, 14:13

    status-report.ts:23

    How is ensured that those elements actually exist when the module is loaded? I think we a `DocumentService.ready()` here...
  10. Georg Ringer uploaded patch set 3 CR +1 V +1 11/12/26, 17:02

  11. Georg Ringer commented on patch set 3 11/12/26, 17:02

    status-report.ts:23 Reply

    Done
  12. core-ci voted on patch set 3 V +1 11/12/26, 17:09 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114205

  13. Josef Glatz voted on patch set 3 V +1 11/12/26, 17:30

  14. Josef Glatz voted on patch set 3 CR +1 11/12/26, 19:09

  15. Simon Schaufelberger voted on patch set 3 CR +1 V +1 11/14/26, 22:51

  16. Josua Vogel commented on patch set 3 11/20/26, 11:57

    StatusService.php:50

    After this patch getSystemStatus() has no caller left in the core. As the class is @internal, it could be removed

    StatusReport.fluid.html:24

    new label references should use the translation domain syntax
  17. Georg Ringer uploaded patch set 4 CR +1 V +1 11/20/26, 19:46

  18. Georg Ringer commented on patch set 4 11/20/26, 19:47

    StatusService.php:50 Reply

    Done

    StatusReport.fluid.html:24 Reply

    Done
  19. core-ci voted on patch set 4 V +1 11/20/26, 19:55 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/115086