-
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 Production Release #2965
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
* Enable FsCheck on NetCore * fix
* newbuild * Added xunit variable * Improved PackageTags
* Updated the scheduler docs * Updated the scheduler docs
* cleaning up racy spec for ActorRefProvider resolution * fixed LeaveAsync cancellation task specs * fixed downingproviderspec config * fixed TailChoppingSpec - increase the sleep time to make timeouts less likely on busy systems * added another necessary awaitAssert to ClusterSpec.ClusterSpec.A_cluster_must_cancel_LeaveAsync_task_if_CancellationToken_fired_before_node_
This PR refactors the classes in the Akka.Routing namespace to take advantage of newer C# features. It also simplifies some of the logic in the various routers.
…dling logic to GotCompletionEvent function
Add try..catch block to LazySink
* added comments to internals * updated intellisense comments * added comments for systemmessage * added more local function support
* Add multi platform test flag to build.fsx * Fix failing MNTR (bug)
Protobuf serializer for Exceptions
* kill xunit.console explicitly on each dotnet-xunit exec * kill dotnet too
RememberEntityStarter missing sender fix
* preliminary createmntrnuget step * make createmntrnuget as dep for createnuget * added netcoreapp1.1 publishing * removed manual copy of dotnet executables replaced with dotnet publish output * remove multi
* Changed mailbox requirements error to use proper type * Implemented stashing support for PriorityMailbox * Added Test for stashing support for PriorityMailbox * Fixed spec * ApiApproval * Tweaked Spec parameters Having 50*3 messages expected to be processed in 300ms caused the spec to fail. Surprisingly upping timeout to 30 secs isnt enough. So i lowered the workload instead
… => extractShardId (#2957)
* Serialization reload on settings change * api approver
* switch number and beta * fix mntr versioning and move persistence out of beta * version suffix on mntr nuspec * template values changed
* Renamed files to reflect their single contained type. And added some comments * Added default config setting for plugin and snapshot serializer for json * Updated Serialization API to account new scenario - Updated LocalSnapshotStore - Updated persistence.conf * Updated SQL Integrations to reflect changes * Adjust author info * Api approval * Added spec for testing fallback scenario * Fixed fallback scenario * Fixed filenames and fixes in MessageSerializerRemotingSpec * Fixed MessageSerializerRemoting * Processed remarks * changed copyright header
* Improved Exception serializer on NetCore * Added serializer for ConsistentHashingPool * Added serializer for Config * Moved from Custom TimeSpan to default Duration type in Protobuf * fix * fixed failing ActorSystemSpec
* cssify the logos and other stuff * add links to gitter and github
* outline * wip release notes * typo * expanded release notes * fixed date
Akka.NET v1.3 Development Deployment
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.0 August 11 2017
Feature Release for Akka.NET
Akka.NET 1.3.0 is a major feature release that introduces the significant changes to Akka.NET and its runtime.
.NET Core and .NET Standard 1.6 Support
This release introduces support for .NET Standard 1.6 for our core libraries and .NET Core 1.1 for the MultiNode Test Runner standalone executable. All packages for Akka.NET are dual-released under both .NET 4.5 and .NET Standard 1.6.
As a side note: Akka.NET on .NET 4.5 is not wire compatible with Akka.NET on .NET Core; this is due to fundamental changes made to the base types in the CLR on .NET Core. It's a common problem facing many different serializers and networking libraries in .NET at the moment. You can use a X-plat serializer we've developed here: #2947 - please comment on that thread if you're considering building hybrid .NET and .NET Core clusters.
Akka.Persistence Released to Market
Akka.Persistence has graduated from beta status to stable modules and its interfaces are now considered to be stable. We'll begin updating all of the Akka.Persistence plugins to stable and to add .NET Standard / .NET 4.5 support to each of them as well following this patch.
DocFx-based Documentation Site
Documentation is now generated using DocFx and compiled from within the Akka.NET project rather than a separate documentation repository.
API Changes
This release does not maintain wire format compatibility with the previous release (v1.2.3) inside Akka.Remote; primarily this is due to having to upgrade from Google Protobuf2 to Protobuf3 in order to add .NET Standard support, but we've also taken the liberty of making other serialization improvements while we're at it. So be advised that during an upgrade from 1.2.* to 1.3.* there will be periods of network disruption between nodes using different versions of the service.
Akka.Remote Performance Improvements
Akka.Remote's throughput has been significantly increased.
See the full set of Akka.NET 1.3.0 fixes here.