Repository navigation
Prepare PHP SDK 2.4.1 shutdown cache diagnostics - #171
Conversation
rmcdaniel
left a comment
There was a problem hiding this comment.
Reviewed exact stable head 2d33bd2f005adc65bc10dd9a8836c06a80bed470, tree 39c2dfb1251e5cd884632cea08e76091d145c277. All 33 applicable candidate gates pass in 38626789420; connected cooperation is explicitly skipped.
Against released 2.4.0, the runtime diff is one diagnostic-context field. The nonzero hit/miss/eviction/cold-fallback control and both framework event controls pass. Complete cache/replay/default/authority implementation remains unchanged; unrelated main cooperation changes are excluded. Release metadata and quickstart are coherent at 2.4.1.
Ready for identical-tree merge and fresh exact merged qualification. Tag, publication, normal registry-installed verification, declared HTTP smoke and stable-tag portal acceptance remain pending. This does not complete #112's optional application measurements.
|
PHP 2.4.1 is published at GitHub release publication is verified at 19:59:44 UTC. The first ordinary anonymous Packagist read immediately afterward still lists 2.4.0 as latest, so normal registry installation is pending rather than claimed. Next: registry/source/dist verification, declared Server HTTP smoke, normal installed Laravel/Symfony diagnostic controls and stable-tag portal acceptance. Source #170 merge remains held until installed qualification. #112's application cache/loss and measurements remain separate. |
Published and installedPHP SDK 2.4.1 normal pinned and bare Composer resolution agree on source/dist Normal registry-only consumers on PHP 8.5.11 / Composer 2.10.3 pass the tagged Laravel 12.69.3 and Symfony framework-bundle/console 7.4.20 compatibility fixtures. The managed cache controls exercise eviction and authoritative history fallback, then assert the actual final counters arrive in the existing framework shutdown events. Laravel's configuration-cache/credential-isolation fixture also passes. These are constructed transport controls, distinct from real Server execution and the unfinished #112 workload. Each consumer retains normal dependency/security resolution, with no advisory bypass. The published actual HTTP smoke passes against declared Server 2.5.0. The stable-tag portal build/deploy/browser checks pass, and the live deployment audit binds the exact published All local consumer containers are removed. Their complete dependency/cache/scratch trees are deleted after this receipt. Main #170 metadata/docs alignment remains on its own final gates. #112's real cache/loss tests and measurements, #169 and frozen Cloud/shared cohorts remain separate. |
|
2.4.1 release alignment is complete. Published tag/source/dist Main #170 merged as Normal registry-only bare, Laravel 12.69.3 and Symfony 7.4 framework consumers agree on 2.4.1 metadata/source/dist and loaded Worker hash; existing framework configuration and real shutdown diagnostic forwarding controls pass. Those synthetic framework transports do not establish full #112/Octane or Nexus execution. Published diagnostics add actual lifetime cache counters to the existing The optional #169 application has separately adopted only the normal 2.4.1 package and is continuing its actual runtime cache qualification. No Cloud, frozen cohort, shared dependency or major-version promotion follows. |
Compatible stable patch
Prepare PHP SDK 2.4.1 from normally published 2.4.0 /
821716a92f179ec360e045c28979a86a5f587075.Backport only PR #170's existing history-cache counters in the
worker.stoppeddiagnostic, its focused logging/framework controls and documentation. Update product-train and quickstart metadata. The runtime diff is one diagnostic-context field; cache behavior, task authority, protocol defaults and request content stay unchanged. Unrelated pending source capability work is excluded.Required qualification
The release is not published or installed-qualified yet. #112's cache/lifecycle and measured HTTP comparison criteria remain open; PR #169 stays a separate optional application candidate.