Repository navigation
Bump Akka.Hosting from 1.5.58 to 1.5.72 - #241
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
force-pushed
the
dependabot/nuget/Akka.Hosting-1.5.71
branch
from
September 10, 2026 16:36
ceb9c04 to
2446fe1
Compare
--- updated-dependencies: - dependency-name: Akka.Hosting dependency-version: 1.5.71 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/nuget/Akka.Hosting-1.5.71
branch
from
September 11, 2026 13:40
2446fe1 to
5686144
Compare
Contributor
Author
|
Looks like Akka.Hosting is updatable in another way, so this is no longer needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pinned Akka.Hosting at 1.5.72.
Release notes
Sourced from Akka.Hosting's releases.
1.5.72
1.5.72 October 3rd, 2026
Akka.NET v1.5.72 backports a non-blocking Cluster extension startup, test-infrastructure hardening, a Cluster.Sharding hand-over fix, and a batch of de-flaked specs from
dev.Starting with this release, Akka.Hosting ships from this repository. The
Akka.Hosting,Akka.Remote.Hosting,Akka.Cluster.Hosting,Akka.Persistence.Hosting,Akka.Hosting.TestKit, andAkka.Hosting.TestKit.Xunit2packages are now built, tested, and published alongside every Akka.NET release at the same version number.Akka.Hosting
src/contrib/hostingand share the Akka.NET version and release cadence. No package IDs, namespaces, or public APIs changed; bumpAkka.Hosting.*to the same version asAkka.*. Hosting-only hotfix versions (such as1.5.60.1) no longer exist: a Hosting fix ships in the next Akka.NET patch release. The documentation moved to getakka.net/articles/hosting. The akkadotnet/Akka.Hosting repository will be archived and keeps the full commit history and release notes for versions up to 1.5.71; the import was taken from commitcefe3c4c.Akka,Akka.DependencyInjectionand allAkka.Hosting.*packages now requireMicrosoft.Extensions.*10.0.0 or later (previously 6.0 for the core packages and 9.0 for Akka.Hosting). The 10.0 packages still shipnetstandard2.0assets, so applications on .NET Framework 4.8, .NET 6 and .NET 8 keep working; NuGet will lift the transitiveMicrosoft.Extensions.*references in those applications to 10.0.x. Akka.Hosting'sOpenTelemetrydependency moves to 1.15.3 or later, which clears GHSA-g94r-2vxg-569j.Akka.TestKit / Akka.TestKit.Xunit
Akka.TestKit.Xunit.TestKitnow implementsInitializeAsync/DisposeAsyncdirectly instead of relying on a derived class's own no-op overrides. Breaking change: a derived spec that already declares its ownInitializeAsync/DisposeAsyncmust mark themoverrideand call the base method, or the build fails withCS0114.Dispose(bool)no longer terminates theActorSystemby itself; the publicDispose()/DisposeAsync()entry points do, after calling the base chain.TestKitBase.ShutdownAsyncoverloads shut anActorSystemdown without blocking a thread pool worker.ConductorBindExceptionandConductorPortSentineltypes, and a 20-minute backstop that kills a node process that never exits on its own.Akka.Streams
ServerBinding.Unbind()used to always wait out the subscription timeout even when no connection was pending. It now completes right away in that case, and still correctly waits when a connection was accepted but never subscribed to.Akka.Cluster.Sharding
updating-state-timeout(5 seconds by default), matching whatreference.confalways documented, instead ofwaiting-for-state-timeout(2 seconds). Migration: if you raisedwaiting-for-state-timeoutto give a slow remember-entities store more time, move that value toupdating-state-timeoutinstead - it no longer affects the write path.ShardRegionthat isn't leaving the cluster, which used to leave that region permanently unusable for the life of the process.Akka.DistributedData
Replicatorstarted after a member had already begun leaving no longer silently drops that member's writes and gossip.Akka.Cluster
akka.cluster.prune-gossip-tombstones-after). The wire change is rolling-upgrade compatible: older nodes ignore the added protobuf field and upgraded nodes treat its absence as an empty tombstone set. Protection becomes fully effective after every node is upgraded; removals that occur while old nodes remain in the cluster are not guaranteed to retain their tombstones.Clusterconstructor no longer blocks on a 20 second ask, andakka.actor.creation-timeoutis no longer consulted by Akka.Cluster at all (Akka.Cluster.Sharding still uses it to bound its own start-up asks). This removes the "Failed to startup Cluster" failure mode, which could shut down a healthy node whenever every thread the startup needed was parked - a small fork-join or other dedicated dispatcher pool, or a stock pool starved under load. Behavior note:Cluster.Get()now returns before core initialization completes, and the cluster's internal actor tree (/system/cluster/core,/system/cluster/core/daemon,/system/cluster/heartbeatReceiver) is created afterCluster.Get()returns rather than before it. All public cluster APIs are message-based, so typical code is unaffected; code that usedCluster.Get()as a "core is started" synchronization point, or that resolves one of those internal paths right after obtaining the extension, should awaitJoinAsync/RegisterOnMemberUpor a cluster event instead.Subscribe,Join,Leave,Down, ...) now route through/system/clusterfor the entire lifetime of the extension - two extra local mailbox hops on this low-traffic control plane - instead of switching to a direct core-daemon reference once startup resolves one, so back-to-back commands from one caller stay in order for good, not just during startup. A lostLeaveno longer wedges every laterLeaveAsync()for the life of the process. Behavior note: callingLeave()/LeaveAsync()again after the extension has already shut down now produces a dead-letteredClusterUserAction.Leave- worth knowing about for dead-letter alerting orEventFilter.DeadLetterassertions.Testing
ResolveOneagainst/system/cluster/core/daemon/downingProviderraced the async cluster-extension init #8359 introduces above; replaced with a dilated retrying resolve, a dynamic port, and an asyncTaskCompletionSourcemember-up signal.3 contributors since release 1.5.71
To see the full set of changes in Akka.NET v1.5.72, click here.
Changes:
... (truncated)
1.5.71
1.5.71 August 26th, 2026
Akka.NET v1.5.71 is a maintenance release that fixes a Cluster Sharding private-replicator recovery bug, hardens MultiNodeTestRunner conductor reliability, flushes graceful
DisassociatePDUs before transport force-close on shutdown, and resolves a handful of TestKit, ClusterClientDiscovery, and DotNetty fixes.Akka.Cluster.Sharding
ClusterShardingReplicatorResiliencySpeccovering the recovery path.Akka.Remote
DisassociatePDUs before transport force-close on shutdown: Ensures in-flight gracefulDisassociatecontrol messages are flushed to the wire before the transport force-closes the connection on shutdown, preventing an abrupt teardown from silently dropping them.Akka.Remote.TestKit (MultiNodeTestRunner)
BarrierCoordinator,Conductor,Controller,Player, andRemoteConnectionagainst conductor-side races and disconnect handling, reducing multi-node spec flakiness.Akka.TestKit
PromiseActorRef.GetPaththat madePathreturn null: Fixes a torn read inPromiseActorRef.GetPaththat could returnnullunder concurrent access.ExpectMsgAsync<T>(Func<T, IActorRef, bool>, ...): Fixes a bug where the overload ofExpectMsgAsyncthat takes a predicate could apply its timeout dilation twice, causing spurious timeout failures.Akka.Cluster.Tools
ClusterClientDiscoverykeeps its contact-point subscriptions alive across rediscovery cycles instead of dropping them.Tests
ClusterShardingQueriesSpecstats/region-state queries converge-then-assert (async): HardensClusterShardingQueriesSpecby making its stats and region-state query assertions wait for convergence before asserting, reducing CI flakiness.1 contributor since release 1.5.70
To see the full set of changes in Akka.NET v1.5.71, click here.
Changes:
See More
... (truncated)
1.5.70
1.5.70 July 2nd, 2026
Akka.NET v1.5.70 is a maintenance release that adds a new "last-N" query offset to Akka.Persistence.Query, resolves two Akka.Streams reliability issues and improves
BroadcastHubperformance under high consumer counts, and fixes a consistent-hashing router bug that could wedge an entire cluster after a 32-bit hash collision.Akka.Persistence.Query
Offset.FromEnd(int count)— "last-N events" query offset: IntroducesOffset.FromEnd(int count), a new query-input-only offset type that begins a read journal query at the Nth event from the end of history rather than from the beginning. The offset is resolved at stream materialization into a concreteSequencestart position; no interface changes or wire-format changes are required. Includes opt-in TCK spec (FromEndOffsetSpec) for plugin authors.Akka.Streams Bug Fixes
Source.From(IAsyncEnumerable<T>)where the underlying enumerator could be disposed before all elements were delivered to downstream, causingObjectDisposedExceptionon high-throughput pipelines.ChannelSinkdrops final element on backpressure - Fixes #8285:ChannelSinkwas discarding the last element in a sequence whenever the downstreamChannel<T>applied backpressure during completion. The sink now correctly delivers all elements before signaling completion.Akka.Streams Performance
BroadcastHubwhen many consumers are attached by optimizing the internal consumer-wheel iteration, yielding measurable throughput improvements at high fan-out.Akka.Core Bug Fixes
ConsistentHash.Createthrew"An entry with the same key already exists". The consistent-hashing router swallowed the exception and returnedNoRouteefor every subsequent message until a manual restart. The ring now linear-probes to the next free slot on a collision instead of throwing. This keeps the hash distribution unchanged and produces a byte-identical ring to prior versions whenever no collision occurs (safe for rolling upgrades), and also protectsAkka.Cluster.Tools'ClusterReceptionist, which builds the same ring.2 contributors since release 1.5.69
To see the full set of changes in Akka.NET v1.5.70, click here.
Changes:
See More
... (truncated)
1.5.70-beta2
1.5.70-beta2 June 30th, 2026
Akka.NET v1.5.70-beta2 is a beta release with a bug fix for
ChannelSinkdropping the final element under backpressure.Akka.Streams Bug Fixes
ChannelSinkdrops final element on backpressure - Fixes #8285:ChannelSinkwas discarding the last element in a sequence whenever the downstreamChannel<T>applied backpressure during completion. The sink now correctly delivers all elements before signaling completion.2 contributors since release 1.5.70-beta1
Changes:
This list of changes was auto generated.
1.5.70-beta1
1.5.70-beta1 June 23rd, 2026
Akka.NET v1.5.70-beta1 is a beta release with a new
Offset.FromEndquery offset for Akka.Persistence.Query, bug fixes forAkka.Streamsasync enumerable disposal, and a performance improvement forBroadcastHubwith high consumer counts.Akka.Persistence.Query
Offset.FromEnd(int count)— "last-N events" query offset: IntroducesOffset.FromEnd(int count), a new query-input-only offset type that begins a read journal query at the Nth event from the end of history rather than from the beginning. The offset is resolved at stream materialization into a concreteSequencestart position; no interface changes or wire-format changes are required. Includes opt-in TCK spec (FromEndOffsetSpec) for plugin authors.Akka.Streams Bug Fixes
Source.From(IAsyncEnumerable<T>)where the underlying enumerator could be disposed before all elements were delivered to downstream, causingObjectDisposedExceptionon high-throughput pipelines.Akka.Streams Performance
BroadcastHubwhen many consumers are attached by optimizing the internal consumer-wheel iteration, yielding measurable throughput improvements at high fan-out.1 contributor since release 1.5.69
Changes:
This list of changes was auto generated.
1.5.69
1.5.69 June 12th, 2026
Akka.NET v1.5.69 is a maintenance release with bug fixes for Akka.DistributedData state propagation, Akka.Core message rejection handling, and Akka.Streams tracing reliability and backpressure cancellation.
Akka.Streams
.Async()actor boundary - Fixes #8243: With stream tracing enabled, per-element trace context was dropped at the publisher/subscriber actor boundary introduced by.Async(), leaving downstream stages with no ambientActivityContext. Trace context now flows correctly across fused interpreter shells.OfferAsync(T, CancellationToken)toISourceQueue<T>— enables cancellation of backpressured pending offers without emitting the cancelled element.Akka.Streams Bug Fixes
NullReferenceExceptionin theGraphInterpreterwhen tracing across actor boundaries — the interpreter now safely handles null activity context references during stream teardown.Akka.Core
RejectOnType<TMessage>should useRejection, notFailure- Fixes #8231:RejectOnTypenow correctly wraps rejected messages asRejectionrather than throwing aFailure, matching the expected stream contract.Akka.DistributedData
ORSetandLWWDictionary, leading to data inconsistencies during node merges.1 contributor since release 1.5.68
Akka.NET v1.5.68 is a maintenance release with bug fixes for Akka.IO TCP connection handling, Akka.Streams stream materialized task faults, and Akka.TestKit xUnit 3 parallel context management.
Akka.IO Bug Fixes
Tcp.CommandFailedwhen a scheduled connect retry throws - Fixes #8195: On Linux, a dropped TCP connection could permanently stall the user actor — it never receivedTcp.ConnectedorTcp.CommandFailedbecause aPlatformNotSupportedExceptionthrown during a scheduled connect retry was swallowed by theHashedWheelTimerScheduler. The retry is now scheduled as aRetryConnectself-message viaIWithTimers, ensuring any exception is surfaced to the commander asTcp.CommandFailedand the connection actor stops cleanly. The pending timer is also canceled automatically when the actor stops, removing a latent use-after-dispose bug.Akka.Streams Bug Fixes
IgnoreSink,QueueSource, andLazySinknow observe their internal materializedTaskfaults, preventing them from surfacing later asUnobservedTaskExceptionevents on the thread pool.Akka.TestKit Bug Fixes
SynchronizationContextinActorCellKeepingSynchronizationContext-ActorCellKeepingSynchronizationContextnow accepts an optional innerSynchronizationContextand delegates scheduling to it while wrapping callbacks with the cell-pinning window. This prevents test hangs in downstream consumers such asAkka.Hosting.TestKitwhose asyncIHostlifecycle depends on xUnit v3'sMaxConcurrencySyncContextscheduling.1 contributor since release 1.5.67
To see the full set of changes in Akka.NET v1.5.68, click here.
Changes:
... (truncated)
1.5.68
1.5.68 May 17th, 2026
Akka.NET v1.5.68 is a maintenance release with bug fixes for Akka.IO TCP connection handling, Akka.Streams stream materialized task faults, and Akka.TestKit xUnit 3 parallel context management.
Akka.IO Bug Fixes
Tcp.CommandFailedwhen a scheduled connect retry throws - Fixes #8195: On Linux, a dropped TCP connection could permanently stall the user actor — it never receivedTcp.ConnectedorTcp.CommandFailedbecause aPlatformNotSupportedExceptionthrown during a scheduled connect retry was swallowed by theHashedWheelTimerScheduler. The retry is now scheduled as aRetryConnectself-message viaIWithTimers, ensuring any exception is surfaced to the commander asTcp.CommandFailedand the connection actor stops cleanly. The pending timer is also canceled automatically when the actor stops, removing a latent use-after-dispose bug.Akka.Streams Bug Fixes
IgnoreSink,QueueSource, andLazySinknow observe their internal materializedTaskfaults, preventing them from surfacing later asUnobservedTaskExceptionevents on the thread pool.Akka.TestKit Bug Fixes
SynchronizationContextinActorCellKeepingSynchronizationContext-ActorCellKeepingSynchronizationContextnow accepts an optional innerSynchronizationContextand delegates scheduling to it while wrapping callbacks with the cell-pinning window. This prevents test hangs in downstream consumers such asAkka.Hosting.TestKitwhose asyncIHostlifecycle depends on xUnit v3'sMaxConcurrencySyncContextscheduling.1 contributor since release 1.5.67
To see the full set of changes in Akka.NET v1.5.68, click here.
Changes:
This list of changes was auto generated.
1.5.67
1.5.67 April 25th, 2026
Akka.NET v1.5.67 is a hotfix release that reverts a breaking change to the persistence plugin contract introduced in v1.5.66.
Akka.Persistence: Revert async
WriteMessagesAsync/SaveAsyncdispatch (#8163)v1.5.66 added
Task.Yield()insideAsyncWriteJournal.ExecuteBatchandSnapshotStoreto move persistence pluginWriteMessagesAsync/SaveAsynccalls off the actor thread. While this improved throughput in benchmarks, it silently broke the implicit contract that persistence plugins rely on — that the synchronous preamble of these methods executes in actor context.This caused failures in plugins that:
SelfinsideWriteMessagesAsync(e.g. Akka.Persistence.Sql, Akka.Persistence.EventStore) — throwsNotSupportedExceptionoff the actor threadDictionary<string, Task>) — concurrent access from actor thread and thread pool causesInvalidOperationExceptionThis release removes the
Task.Yield()calls and restores the original dispatch behavior. A future version may reintroduce this optimization with a more targeted approach that preserves the plugin threading contract.If you are on v1.5.66, upgrade to v1.5.67 immediately if you use any third-party persistence plugin.
Changes:
This list of changes was auto generated.
1.5.66
1.5.66 April 24th, 2026
Akka.NET v1.5.66 is a significant release with persistence bug fixes, major Akka.Streams improvements including OpenTelemetry trace propagation and non-blocking materialized values, and new serialization security controls.
Akka.Streams: OpenTelemetry Trace Context Propagation
Akka.Streams now propagates
System.Diagnostics.Activitytrace context end-to-end through stream graphs, including across async stage boundaries, fan-in merges, and fan-out broadcasts. This enables full distributed tracing visibility into stream pipelines when using OpenTelemetry.For full documentation, see: https://getakka.net/articles/streams/stream-tracing.html
Akka.Streams: Non-Blocking Materialized-Value TaskCompletionSource
All
TaskCompletionSourceinstances used for materialized values across Akka.Streams now useTaskCreationOptions.RunContinuationsAsynchronously, eliminating potential deadlocks and thread-pool starvation when continuations run synchronously on completion.Akka.Persistence
Akka.Core
New Features
allow-unregistered-typesserialization setting — when set tofalse,FindSerializerForTypethrowsSerializationExceptionif no explicit serializer binding exists, rather than falling back to the default serializer.Documentation
4 contributors since release 1.5.65
To see the full set of changes in Akka.NET v1.5.66, click here.
Changes:
... (truncated)
1.5.65
1.5.65 April 10th, 2026
Akka.NET v1.5.65 is a maintenance release with important bug fixes for Akka.Cluster.Sharding, Akka.Core configuration, and Akka.TestKit.
Akka.Cluster.Sharding Bug Fixes
ShardStoppedsafety net from #8055 fires spuriously after every successful rebalance, causing the same shard to be allocated to 2+ nodes simultaneously.AwaitingLeasestashesHandOffmessages indefinitely, preventing the coordinator from reclaiming stuck shards.StartShardRebalanceIfNeededsilently skips shards during graceful shutdown when a rebalance is already in progress.Akka.Core Bug Fixes
Settings.InjectTopLevelFallbackthat could cause configuration corruption under concurrent access.Akka.TestKit Bug Fixes
IAsyncLifetime.1 contributor since release 1.5.64
To see the full set of changes in Akka.NET v1.5.65, click here.
Changes:
This list of changes was auto generated.
1.5.64
1.5.64 March 31st, 2026
Akka.NET v1.5.64 is a maintenance release focused on completing the xUnit 3 migration for TestKit packages, removing the FluentAssertions transitive dependency, and merging the Multi-Node Test Runner back into the core repository.
FluentAssertions Removal
Due to the recent commercialization of FluentAssertions, we have completed the removal of the FluentAssertions transitive dependency from all
Akka.TestKit.*packages. If your tests relied on the transitive FluentAssertions dependency provided by Akka.NET TestKit packages, you will need to add a direct reference to FluentAssertions in your own project.TestKit Package Naming Convention
As part of the ongoing xUnit 3 migration, TestKit packages now follow a naming convention: packages with the
.Xunitpostfix provide xUnit 3 support, while packages with the.Xunit2postfix provide xUnit 2 support.Akka.TestKit.*packages.Akka.Cluster.TestKitto xUnit 3.Akka.MultiNode.TestAdapterto xUnit 3.1 contributor since release 1.5.63
To see the full set of changes in Akka.NET v1.5.64, click here.
Changes:
This list of changes was auto generated.
1.5.63
1.5.63 March 24th, 2026
Akka.NET v1.5.63 is a maintenance release that includes a critical Akka.Remote bug fix along with Akka.Streams fixes and a major migration of all test projects to xUnit 3.
All users running Akka.Remote or Akka.Cluster are strongly encouraged to upgrade.
QueueSource.UnfoldResourceAsyncSource.Important Akka.Remote Bug Fix
Fixes a critical issue where a stale ACK from a previous connection could cause an irrecoverable quarantine state after a transient network disruption, permanently preventing nodes from re-establishing communication.
In affected scenarios, the only recovery option was a full restart of the quarantined node. This fix ensures that stale ACKs are correctly discarded during reconnection, allowing nodes to recover automatically after network interruptions.
2 contributors since release 1.5.62
To see the full set of changes in Akka.NET v1.5.63, click here.
Changes:
See More
... (truncated)
1.5.62
1.5.62 March 3rd, 2026
Akka.NET v1.5.62 is a maintenance release with an important bug fix for logging stability when using third-party logging providers.
Bug Fixes
1 contributor since release 1.5.61
To see the full set of changes in Akka.NET v1.5.62, click here.
Changes:
This list of changes was auto generated.
1.5.61
1.5.61 February 26th, 2026
Akka.NET v1.5.61 is a maintenance release with important bug fixes for Akka.Cluster.Sharding, Akka.Cluster, and Akka.Core.
Akka.Cluster.Sharding Bug Fixes
Entitiesclass was initialized with the wrongRememberEntitiesflag.ResendShardHosthandler compared a region variable to itself instead of comparing against the message's region.Akka.Cluster Bug Fixes
!=operator which incorrectly delegated toIsConcurrentWithinstead of being the logical negation of==, and fixes the<operator to correctly exclude the equal case.LogInfooverload used the wrong format index.Bug Fixes
randomFactorparameter type frominttodoubleto match the expected behavior for jitter calculations.ClusterHeartbeat,ShardRegion, andSinkRefImpl.Improvements
Askoperations.4 contributors since release 1.5.60
To see the full set of changes in Akka.NET v1.5.61, click here.
Changes:
See More
... (truncated)
1.5.60
1.5.60 February 9th, 2026
Akka.NET v1.5.60 is a maintenance release with a bug fix and a new feature for structured logging.
Bug Fixes
TestActorcould receive messages before its initialization was complete when tests were run in parallel, causing intermittent test failures.New Features
Add logging context enrichment and scopes - Fixes issue #7535. Adds
WithContext()andBeginScope()extension methods toILoggingAdapterfor structured logging context enrichment. Context properties are automatically included in log output and forwarded to downstream logging providers like Serilog and NLog. See documentation.To see the full set of changes in Akka.NET v1.5.60, click here.
Changes:
This list of changes was auto generated.
1.5.59
1.5.59 January 27th, 2026
Akka.NET v1.5.59 is a maintenance release with critical bug fixes and new features for observability.
Critical Bug Fixes
Seentable contained addresses of members that had already left the cluster.Bug Fixes
Inbox.AwaitResultnow correctly throwsTimeoutExceptionwhen a timeout occurs, rather than wrapping it in anAggregateException.DeferAsyncwith an async handler would throw "RunTask calls cannot be nested" when called fromCommandAsync.AwaitAssertAsyncin Akka.TestKit to correctly wait for the full timeout duration before failing assertions.New Features
System.Diagnostics.ActivityContextwhen created, enabling correlation between Akka.NET logs and distributed traces in observability platforms like OpenTelemetry, Application Insights, and Jaeger.startAfterNrOfConsumersparameter toBroadcastHub.Sink<T>()that delays broadcasting until the specified number of consumers have subscribed:Improvements
CoordinatedShutdownnow logs the specific reason for shutdown at INFO level, making it easier to diagnose why an actor system terminated.To see the full set of changes in Akka.NET v1.5.59, click here.
Changes:
See More
This list of changes was auto generated.
Commits viewable in compare view.