Repository navigation
Report existing history-cache counters at worker shutdown - #170
Conversation
|
The first candidate exposed a test-fixture mistake: the new managed cache lifecycle shared Laravel's logger with an existing shutdown-only assertion. Current head The original Symfony 6.4/7 jobs separately failed downloading PHPStan with HTTP 429 from GitHub before behavioral/static checks; no cause beyond that response is inferred. Those original failures remain recorded. Fresh normal checks are running on the corrected head; no source or installed acceptance is claimed yet. |
|
Exact head I am requesting one retry of only failed jobs on the same head, commands and limits. The original failures remain recorded. No dependency, transport policy, test expectation or source change is being made for that response. Publication and installed acceptance remain pending. |
|
Exact source The new polled-history cache/logging control and Laravel/Symfony event controls pass. This qualifies source reporting, not a published installation or the optional Octane workload. Stable backport #171 has its own normal gates, reviewed merge, publication and installed verification ahead. Main documentation merge stays held until that stable delivery. |
rmcdaniel
left a comment
There was a problem hiding this comment.
Reviewed final main head f126f174e2c699e40f91f2d67278d2fb576e99bd, tree 5e481de749085a2373f2586d6c74ee86fbea1826. All 33 applicable normal checks pass; connected cooperation is explicitly skipped.
The compatible 2.4.1 release and normal installed acceptance are complete, so the documentation hold is released. This source diff adds the same diagnostic field/tests/docs and aligns version/quickstart metadata to published 2.4.1. Existing main-only cooperative implementation is not included in that stable release.
Ready for merge. Keep the public portal on the qualified stable tag rather than publishing main-only APIs. #112 and #169 retain their actual cache/loss and measurement criteria.
|
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. |
Change
Include the Worker's existing lifetime history-cache counters in the
worker.stoppeddiagnostic context. PSR logs, diagnostic callbacks and Laravel/Symfony events receive the samesticky_cachemap. Shutdown still clears retained history and preserves the counters.This supports #112's actual cache and memory qualification. The earlier qualification refused missing worker-listing telemetry and remains unqualified.
Verification
git diff --checkpass. Hosted PHP/framework, static analysis, dependency and corpus gates are pending.This is diagnostic reporting only. Cache settings, replay behavior, request bodies and task authority are unchanged. The test transport is constructed; installed framework verification and a compatible stable publication are still required. Main documentation merge is held until that publication is qualified. #112 and PR #169 retain their remaining lifecycle and measurement criteria.