-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Akka.NET v1.3.9 Production Release #3577
Merged
Merged
Conversation
This file contains 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
Synchronize 1.4 branch with dev
* Implement PartitionHub * port docs * fix formatting * API approval * address remarks
* AkkaPduCodec performance fixes * made HeartbeatPdu immutable * made all internal formatting methods static
* Tests should be precise - in temrs of what to expect * Ask interface refined #3220 * ClusterRouter unit test fix #3220 * Ask deadlock test added #3220 * Handle deadlock by removing the SynchronizationContext #3220 * Fixing ScatterGather router test #3220 * Ask interface refined #3220 AskSpecs consolidated Api change approval - internal CastTask removed * Fixing header #3220
* fixed bug in UseRoleIgnoredSpec * close #3294 - fixed usages of GetPaths inside all Group router implementations
* expose RemoteActorRef APIs for extensibility * made ClusterActorRefProvider public * created IClusterActorRefProvider marker interface
* added Akka.NET v1.3.4 release notes
* fixed issues with supervision docs * one more bugfix in the example code
* Fixing premature pruning of Topics The DistributedPubSubMediator wasn't checking if the TopicActor was actually terminated before pruning it from the bucket. This can cause problems if a TopicActor is re-suscribed to before being stopped. The Subscribe message only checks Context.Child, but does not check if the bucket is still valid. So it was possible to get in a state where subscribes/unsubscribes were succeeding, but any publishes to the topic where being dropped on the floor. I've also switched from null to ActorRefs.Nobody. Previously, if a Topic actor had terminated and a publish for that topic was received before the DistributedPubSubMediator did a prune, the publish would throw an exception. * Switching to IsNobody() extension method
FunctionRef
* initial commit for StreamRefs * more work over Stream-Ref serializer * fixes in serializer and config * fixes in stream-refs and tests * StreamRefs docs * added defaults for StreamRefsSettings * StreamRefs approvals API * fixed missing impl + added animation gifs to docs * applied docs, fixed namespaces * fixed stream ref serializer namespaces
* Change TaskCompletionSource from TGeneric to Option<TGeneric> * update Code and Unit tests to make them build * Fix TcpSpec.Outgoing_TCP_stream_must_properly_full_close_if_requested Unit Test * Fix KeepGoingStageSpec Unit Tests
added v1.3.9 placeholder for nightlies
* Add CombineMaterialized method to Source * More reasonable materializers combine function name and type * Approve Streams API change * Move instance method to SourceOperations extensions
Ignore CodeRush working files Ignore GhostDoc working files Ignore NDepend working files Ignore Visual Studio Code working files
Messages that come through for an entity before StartEntity has been processed for that entity caused redundant persistence of the entity.
…ities-redundant-journals Sharding - Check remembered entities before remembering entity
This PR fixes various issues w.r.t. the documentation site. - fix various typos - fix several links - fix styling issues
I don't believe `Selet` is a valid method
* ClusterSingletonManager should ignore FSM events during shutdown * added copyright headers and API approval * wasn't calling RunCoordinatedShutdownWhenDowning() before * Run all CoordinatedShutdown phases also when downing * add Reason to CoordinatedShutdown * Allow member to leave a cluster via CoordinatedShutdown.run when MemberStatus is Joining/WeaklyUp/Up. * ClusterSpec, race between MemberRemoved and MemberExited
private readonly double? _lastTemperatureReading = null; on line 61 would make this field not editable because of the red only modifier
* Port KeepAliveConcat and UnfoldFlow * additional KeepAliveConcat test
THe -> The
* KillSwitches: flow stage from CancellationToken * removed cancellation token from materializer value type * added API approvals and docs
* Port PagedSource * Port IntervalBasedRateLimiter
* first cut at Akka.NET v1.3.9 release notes * finished v1.3.9 release notes * added link back to milestone
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.
1.3.9 August 22 2018
Maintenance Release for Akka.NET 1.3
Akka.NET v1.3.9 features some major changes to Akka.Cluster.Sharding, additional Akka.Streams stages, and some general bug fixes across the board.
Akka.Cluster.Sharding Improvements
The Akka.Cluster.Sharding documentation already describes some of the major changes in Akka.NET v1.3.9, but we figured it would be worth calling special attention to those changes here.
Props Factory for Entity Actors
In addition to the existing APIs we've always had for defining sharded entities via
Props
, Akka.NET v1.3.9 introduces a new method overload forStart
andStartAsync
which allows users to pass in theentityId
of each entity actor as a constructor argument to those entities when they start.For example:
This will give you the opportunity to pass in the
entityId
for each actor as a constructor argument into theProps
of your entity actor and possibly other use cases too.Improvements to Starting and Querying Existing Shard Entity Types
Two additional major usability improvements to Cluster.Sharding come from some API additions and changes.
The first is that it's now possible to look up all of the currently registered shard types via the
ClusterSharding.ShardTypeNames
property. So long as aShardRegion
of that type has been started in the cluster, that entity type name will be added to the collection exposed by this property.The other major usability improvement is a change to the
ClusterSharding.Start
property itself. Historically, you used to have to know whether or not the node you wanted to use sharding on was going to be hosting shards (callClusterSharding.Start
) or simply communicated with shards hosted on a different cluster role type (callClusterSharding.StartProxy
). Going forward, it's safe to callClusterSharding.Start
on any node and you will either receive anIActorRef
to activeShardRegion
or aShardRegion
running in "proxy only" mode; this is determined by looking at theClusterShardingSettings
and determining if the current node is in a role that is allowed to host shards of this type.RestartShard
escapes into userspaceAkka.Streams Additions and Changes
In Akka.NET v1.3.9 we've added some new built-in stream stages and API methods designed to help improve developer productivity and ease of use.
KillSwitches: flow stage from CancellationToken
Other Updates, Additions, and Bugfixes
To see the full set of changes for Akka.NET v1.3.9, click here.