…top, idempotent AddAsyncDaemon (#5056) (#5058) Closes #5055, closes #5056. At Kubernetes pod shutdown, any second Pause/Stop pass over the projection coordinator (double AddAsyncDaemon hosted-service registration, user pause + host stop, Wolverine quiesce + host stop) fanned StopAllAsync out over daemons the first pass had already disposed. Reading _cancellation.Token off the disposed CancellationTokenSource threw ObjectDisposedException, logged as "Error while trying to stop daemon agents" once per daemon on every shutdown. JasperFx.Events 2.36.2 (#574/#575) makes the daemon stop path safe after disposal and adds the abstract ClearResolvedDaemons() seam that ProjectionCoordinatorBase.StopAsync calls after disposing daemons. This is the Marten side: - ProjectionCoordinator implements ClearResolvedDaemons() by resetting the _daemons cache, so a repeated Pause/Stop has nothing to fan out over and a later ResumeAsync or daemon accessor builds fresh daemons instead of handing back disposed instances - ExplicitProjectionCoordinator.StopAsync now disposes its daemons after stopping them and clears its cache the same way - Both AddAsyncDaemon overloads skip re-registration when Marten's own coordinator is already registered, so a doubled call can't register a second IHostedService forwarding that stops the same coordinator twice Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Uh oh!

Uh oh!

SelectMany().Select() in the Linq support #575

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions