Under the hood
Plugin and hook execution was rewritten to stream results and track per-handler timing and outcomes
What
The internal system that runs plugin and hook code was rebuilt around async generators (a way of producing a sequence of results piece by piece, or streaming, rather than all at once). The new version:
- streams results in chunks as they become available
- tracks per-handler timing, outcome, and chunk counts
- supports a
.catchhandler with a grace window for handling failures - can chain or hand off execution between different plugin tiers
Why
This is an internal rework of how plugin and hook code runs; the finding does not describe a specific new user-facing capability, but the added timing and outcome tracking suggests better visibility into how hooks and plugins perform and fail.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The practical, user-visible effect of this rewrite (beyond internal timing/outcome tracking) is not specified in the finding.