Bump Akka from 1.4.11 to 1.4.14

[dependabot-preview[bot]]

Bumps Akka from 1.4.11 to 1.4.14.

Release notes

Sourced from Akka's releases.

Akka.NET v1.4.14

1.4.14 December 30 2020

Maintenance Release for Akka.NET 1.4

Akka.NET v1.4.14 contains some significant bug fixes and improvements. It is a highly recommended upgrade for all Akka.NET users.

Major Reduction in Idle CPU Usage and Latency for Akka.Remote One of the most important fixes introduced in Akka.NET v1.4.14 is the new self-tuning batching system for Akka.Remote's DotNetty transport, which simulatneously reduces idle CPU consumption on low-traffic systems by as much as 55% while improving latency by a factor of 10 for low-traffic systems.

The batching system no longer needs to be configured - it can scale up and down with workload automatically in order to both maximize throughput with a minimal amount of latency. You can read more about it here: https://getakka.net/articles/remoting/performance.html

Other bug fixes and improvements:

• Akka: Move RouterActor routing logic controller actor instantiation from OnReceive to constructor
• Akka.Streams: Serializing a SinkRef wrapped inside a POCO failed
• Akka.Persistence: Akka.NET Should Allow Separate Read and Write Event Adapter Bindings
• Akka.Persistence.Query: Added Timestamp to EventEnvelope - breaking API change; will require all Akka.Persistence plugins to be recompiled and updated.
• Akka.Remote: fix NRE inside RemotingTerminator

To see the full set of fixes in Akka.NET v1.4.14, please see the milestone on Github.

COMMITS	LOC+	LOC-	AUTHOR
9	533	370	Aaron Stannard
4	5617	44	Gregorius Soedharmo
1	61	1	Brian Sain
1	207	54	Ismael Hamed

Changes:

• d635f7d1155e1ff33d99f8d5fa4804fee13f3296 Merge pull request #4705 from akkadotnet/dev
• 78483c58968d1d0aa9305ebbd0d58a15144b1591 added v1.4.14 release notes (#4704)
• 5e744ff6621cb3afc436cb30bbaafe5f19e82d58 Update Akka.Remote performance guidance for Akka.NET v1.4.14 (#4703) [ #4685 ]
• 58294a492ad76da87f3c210ca6d847e78cd551ec Create ReadWriteEventAdapter and set if event is bound to separate re… (#4568)
• 7aee504c6c0ce691e77a7f31cfa3749ce44b5c5f SinkRef declared inside a POCO should serialize properly (#4425) [ #4421 ]
• 77cb49f9550ff783a76d597c0091961def22634a cleaned up duplicate TargetFramework tag in Samples.Cluster.Metrics.Common (#4701)
• fe8a5be4c12f6f94570f89eb6047ce8610926050 Move RouterActor routing logic controller actor instantiation from OnReceive to constructor (#4700)
• bfc2f32b7d6fdd89905af40828e34715d098101c Create sample projects for AdaptiveLoadBalancingGroup (#4691)
• 3f0d654495a0abbf32df6dab22b1f783861c7943 fix NRE inside RemotingTerminator (#4686) [ #4677, #7 ]
• b7630e5bf6e81631ace79bf3db0de38818a09f02 Update ActorTaskSchedulerMessage with defensive coding to prevent possible NRE problems in the future. (#4693)

• b8e74e06e6adecd5d4ce13bbfb9ab44d2a75e199 Auto-tuning DotNetty batching + removing scheduler from batching system (#4685)
• 67c6b325842603d8c98ae3b6ecd9bbf41c09f51f fixed bug with IPersistentRepresentation.Update and timestamp propagation (#4684)
• be43227fa20dbd6e353ad2705c9b2df6c0357d31 upgraded to Incrementalist v0.4.0 (#4690)
• 6e1aface3a5c5dd82ecf71c9721d02ffff68a4fd Added Timestamp to EventEnvelope (#4680)
• 55fa6569c159166beb1487dd78431137bab10c91 API - added overload for IScheduler that accepts IRunnable (#4675)
• 91e9c50b8cc6d2f7ba983cd8ceac260c215fd4a2 Move DotNetty batching scheduling off of DotNetty STEE and onto HashedWheelTimer (#4678)
• d14bb5b56f2e4deb2ca1c332babae5670c69ef68 Update RELEASE_NOTES.md

Changelog

Sourced from Akka's changelog.

1.4.14 December 30 2020

Maintenance Release for Akka.NET 1.4

Akka.NET v1.4.14 contains some significant bug fixes and improvements. It is a highly recommended upgrade for all Akka.NET users.

Major Reduction in Idle CPU Usage and Latency for Akka.Remote One of the most important fixes introduced in Akka.NET v1.4.14 is the new self-tuning batching system for Akka.Remote's DotNetty transport, which simulatneously reduces idle CPU consumption on low-traffic systems by as much as 55% while improving latency by a factor of 10 for low-traffic systems.

The batching system no longer needs to be configured - it can scale up and down with workload automatically in order to both maximize throughput with a minimal amount of latency. You can read more about it here: https://getakka.net/articles/remoting/performance.html

Other bug fixes and improvements:

• Akka: Move RouterActor routing logic controller actor instantiation from OnReceive to constructor
• Akka.Streams: Serializing a SinkRef wrapped inside a POCO failed
• Akka.Persistence: Akka.NET Should Allow Separate Read and Write Event Adapter Bindings
• Akka.Persistence.Query: Added Timestamp to EventEnvelope - breaking API change; will require all Akka.Persistence plugins to be recompiled and updated.
• Akka.Remote: fix NRE inside RemotingTerminator

To see the full set of fixes in Akka.NET v1.4.14, please see the milestone on Github.

COMMITS	LOC+	LOC-	AUTHOR
9	533	370	Aaron Stannard
4	5617	44	Gregorius Soedharmo
1	61	1	Brian Sain
1	207	54	Ismael Hamed

1.4.13 December 16 2020

Maintenance Release for Akka.NET 1.4

Akka.NET v1.4.13 includes a number of bug fixes and enhancements:

AppVersion now uses Assembly Version by Default The new AppVersion setting, which is used to communicate application version numbers throughout Akka.Cluster and is used in scenarios such as Akka.Cluster.Sharding to help determine which nodes receive new shard allocations and which ones do not, now uses the following default HOCON setting:

akka.cluster.app-version = assembly-version

By default now the AppVersion communicated inside Akka.Cluster Member events uses the Major.Minor.BuildNumber from the Assembly.GetEntryssembly() or Assembly.GetExecutingAssembly() (in case the EntryAssembly is null). That way any updates made to your executable's (i.e. the .dll that hosts Program.cs) version number will be automatically reflected in the cluster now without Akka.NET developers having to set an additional configuration value during deployments.

Other bug fixes and improvements:

• Akka.IO: UdpExt.Manager: OverflowException when sending UDP packets to terminated clients
• Akka.Configuration / Akka.Streams: Memory Leak when using many short lived instances of ActorMaterializer
• Akka: Deprecate PatternMatch
• Akka: FSM: exception in LogTermination changes stopEvent.Reason to Shutdown
• Akka.Cluster.Tools: ClusterSingleton - Ignore possible state change in start
• Akka.Cluster.Tools: DistributedPubSub - new setting and small fixes

Commits

• d635f7d Merge pull request #4705 from akkadotnet/dev
• 78483c5 added v1.4.14 release notes (#4704)
• 5e744ff Update Akka.Remote performance guidance for Akka.NET v1.4.14 (#4703)
• 58294a4 Create ReadWriteEventAdapter and set if event is bound to separate re… (#4568)
• 7aee504 SinkRef declared inside a POCO should serialize properly (#4425)
• 77cb49f cleaned up duplicate TargetFramework tag in Samples.Cluster.Metrics.Common (#...
• fe8a5be Move RouterActor routing logic controller actor instantiation from OnReceive ...
• bfc2f32 Create sample projects for AdaptiveLoadBalancingGroup (#4691)
• 3f0d654 fix NRE inside RemotingTerminator (#4686)
• b7630e5 Update ActorTaskSchedulerMessage with defensive coding to prevent possible NR...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #78.