Bump Akka from 1.4.33 to 1.4.45

[dependabot[bot]]

Bumps Akka from 1.4.33 to 1.4.45.

Release notes

Sourced from Akka's releases.

Akka.NET v1.4.45

1.4.45 October 19th 2022

Akka.NET v1.4.45 is a patch release for Akka.NET v1.4 for a bug introduced in v1.4.44.

Patch

• Akka.NET: Revert change to ConfigurationException that is causing binary backward compatibility problem

Changes:

• 5f496e8e29b0f3bd2bbd2c8c7ce67fca8aa103cd Update RELEASE_NOTES.md for 1.4.45 release (#6202)
• 90dde2581c8ae903b5cff7c585dcc6a8725ef2aa Revert ConfigurationException due to binary incompatibility (#6201)

This list of changes was auto generated.

Akka.NET v1.4.44

1.4.44 October 17th 2022

Akka.NET v1.4.44 is a maintenance release for Akka.NET v1.4 that contains numerous performance improvements in critical areas, including core actor message processing and Akka.Remote.

Performance Fixes

• remove delegate allocation from ForkJoinDispatcher and DedicatedThreadPool
• eliminate Mailbox delegate allocations
• Reduce FSM<TState, TData> allocations
• removed boxing allocations inside FSM.State.Equals
• Eliminate DefaultLogMessageFormatter allocations

In sum you should expect to see total memory consumption, garbage collection, and throughput improve when you upgrade to Akka.NET v1.4.44.

Other Features and Improvements

• Akka.Cluster and Akka.Cluster.Sharding: should throw human-friendly exception when accessing cluster / sharding plugins when clustering is not running
• Akka.Cluster.Sharding: Add HashCodeMessageExtractor factory
• Akka.Persistence.Sql.Common: Fix DbCommand.CommandTimeout in BatchingSqlJournal

You can see the full list of fixes in Akka.NET v1.4.44 here.

COMMITS	LOC+	LOC-	AUTHOR
10	651	69	@​Aaronontheweb
4	275	17	@​Arkatufus

Changes:

• 79c652fa5a7eb18d1c4aee5cdf1739fb48018272 added v1.4.44 release notes (#6197)
• 183ec5ae1229b2948e1b18c2e90aa75eb52f8955 removed boxing allocations inside FSM (#6183)
• cc3a36141e0d3ae8b066d0cc287057d7eef01009 [BACKPORT #6173] Add HashCodeMessageExtractor factory (#6182)
• aca6850eb68bbdb64f029bad019d3e58e4bb290f Fix DbCommand.CommandTimeout (#6175) (#6180)
• 7e9e58f24c65932e032af813f8839afa79ea8c0d [BACKPORT #6166] Eliminate DefaultLogMessageFormatter allocations (#6168)
• 5f8710d9ce016227b1e73e9c2dc1957f74508b19 Improve error/exception message for misconfigured cluster provider (#6167)

... (truncated)

Changelog

Sourced from Akka's changelog.

1.4.45 October 19th 2022

Akka.NET v1.4.45 is a patch release for Akka.NET v1.4 for a bug introduced in v1.4.44.

Patch

• Akka.NET: Revert change to ConfigurationException that is causing binary backward compatibility problem

1.4.44 October 17th 2022

Akka.NET v1.4.44 is a maintenance release for Akka.NET v1.4 that contains numerous performance improvements in critical areas, including core actor message processing and Akka.Remote.

Performance Fixes

• remove delegate allocation from ForkJoinDispatcher and DedicatedThreadPool
• eliminate Mailbox delegate allocations
• Reduce FSM<TState, TData> allocations
• removed boxing allocations inside FSM.State.Equals
• Eliminate DefaultLogMessageFormatter allocations

In sum you should expect to see total memory consumption, garbage collection, and throughput improve when you upgrade to Akka.NET v1.4.44.

Other Features and Improvements

• Akka.Cluster and Akka.Cluster.Sharding: should throw human-friendly exception when accessing cluster / sharding plugins when clustering is not running
• Akka.Cluster.Sharding: Add HashCodeMessageExtractor factory
• Akka.Persistence.Sql.Common: Fix DbCommand.CommandTimeout in BatchingSqlJournal

You can see the full list of fixes in Akka.NET v1.4.44 here.

COMMITS	LOC+	LOC-	AUTHOR
10	651	69	@​Aaronontheweb
4	275	17	@​Arkatufus

1.4.42 September 23 2022

Akka.NET v1.4.42 is a minor release that contains some minor bug fixes.

• DData: Suppress gossip message from showing up in debug log unless verbose debug logging is turned on

• TestKit: TestKit automatically injects the default TestKit default configuration if an ActorSystem is passed into its constructor

• Sharding: Added a new GetEntityLocation query message to retrieve an entity address location in the shard region

  In order to use this query, "remember entities" should be turned on or the provided shard IMessageExtractor supports the ShardRegion.StartEntity message. Complete documentation can be read here

If you want to see the full set of changes made in Akka.NET v1.4.42, click here.

COMMITS	LOC+	LOC-	AUTHOR
3	66	3	Gregorius Soedharmo
1	557	118	Aaron Stannard

1.4.41 August 31 2022

Akka.NET v1.4.41 is a minor release that contains some minor bug fix and throughput performance improvement for Akka.Remote

... (truncated)

Commits

• 5f496e8 Update RELEASE_NOTES.md for 1.4.45 release (#6202)
• 90dde25 Revert ConfigurationException due to binary incompatibility (#6201)
• 79c652f added v1.4.44 release notes (#6197)
• 183ec5a removed boxing allocations inside FSM (#6183)
• cc3a361 [BACKPORT #6173] Add HashCodeMessageExtractor factory (#6182)
• aca6850 Fix DbCommand.CommandTimeout (#6175) (#6180)
• 7e9e58f [BACKPORT #6166] Eliminate DefaultLogMessageFormatter allocations (#6168)
• 5f8710d Improve error/exception message for misconfigured cluster provider (#6167)
• 23e5d92 make DedicatedThreadPool.QueueUserWorkItem\<T> generic (#6156)
• 234bb8f Reduce FSM\<TState, TData> allocations (#6145)
• 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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[dependabot[bot]]

Superseded by #442.