petabridge / NBench

Performance benchmarking and testing framework for .NET applications :chart_with_upwards_trend:
https://nbench.io/
Apache License 2.0
532 stars 46 forks source link

Bump Akka from 1.4.33 to 1.5.10 #462

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps Akka from 1.4.33 to 1.5.10.

Release notes

Sourced from Akka's releases.

akka.net v1.5.10

1.5.10 July 26th 2023

Akka.NET v1.5.9 is a maintenance release with a minor API change.

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

COMMITS LOC+ LOC- AUTHOR
1 70 12 Gregorius Soedharmo

1.5.9 July 18th 2023

Akka.NET v1.5.9 is a maintenance release that introduces some performance improvements and internal code cleanup/modernization.

Changes:

Improvements:

Code modernization:

Update dependency versions:

Akka.TestKit.Xunit Changes

Due to breaking API change in Xunit 2.5.0, updating to Akka.NET 1.5.9 might break your unit tests. Some of the breaking change that we've noticed are:

  • AkkaEqualException constructor has been changed due to changes in Xunit API. If you're using this class, please use the AkkaEqualException.ForMismatchedValues() static method instead of using the constructor.
  • Testing for exception types by calling async code inside a sync delegate will not unwrap the AggregateException thrown. Either use async all the way or manually unwrap the exception.
  • Xunit Asset.Equal() does not automatically check for collection item equality anymore, that means doing Assert.Equal() between two dictionary or list would not work anymore.
  • Some Xunit classes have been changed from public to private. If you're using these classes, you will need to refactor your code.
  • FsCheck.Xunit: Xunit Roslyn analyzer has become a bit too overzealous and insists that all unit test method can only return either void or Task and will raise a compilation error if you tried to return anything else. If you're using FsCheck.Xunit, you will need to use a pragma to disable this check: #pragma warning disable xUnit1028.

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

| COMMITS | LOC+ | LOC- | AUTHOR |

... (truncated)

Changelog

Sourced from Akka's changelog.

1.5.10 July 26th 2023

Akka.NET v1.5.9 is a maintenance release with a minor API change.

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

COMMITS LOC+ LOC- AUTHOR
1 70 12 Gregorius Soedharmo

1.5.9 July 18th 2023

Akka.NET v1.5.9 is a maintenance release that introduces some performance improvements and internal code cleanup/modernization.

Changes:

Improvements:

Code modernization:

Update dependency versions:

Akka.TestKit.Xunit Changes

Due to breaking API change in Xunit 2.5.0, updating to Akka.NET 1.5.9 might break your unit tests. Some of the breaking change that we've noticed are:

  • AkkaEqualException constructor has been changed due to changes in Xunit API. If you're using this class, please use the AkkaEqualException.ForMismatchedValues() static method instead of using the constructor.
  • Testing for exception types by calling async code inside a sync delegate will not unwrap the AggregateException thrown. Either use async all the way or manually unwrap the exception.
  • Xunit Asset.Equal() does not automatically check for collection item equality anymore, that means doing Assert.Equal() between two dictionary or list would not work anymore.
  • Some Xunit classes have been changed from public to private. If you're using these classes, you will need to refactor your code.
  • FsCheck.Xunit: Xunit Roslyn analyzer has become a bit too overzealous and insists that all unit test method can only return either void or Task and will raise a compilation error if you tried to return anything else. If you're using FsCheck.Xunit, you will need to use a pragma to disable this check: #pragma warning disable xUnit1028.

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

COMMITS LOC+ LOC- AUTHOR

... (truncated)

Commits
  • 12a5434 Update RELEASE_NOTES.md for 1.5.10 release (#6852)
  • 745520e Bump Verify.Xunit from 20.4.0 to 20.6.0 (#6848)
  • 47a1883 Add constructor with ActorSystemSetup argument to SnapshotStoreSerializationS...
  • fe9c570 Update RELEASE_NOTES.md for 1.4.9 release (#6840)
  • 8580932 made transport adapter components public (#6838)
  • 54f4967 Bump XunitVersion from 2.4.2 to 2.5.0 (#6825)
  • 15635b5 Harden LWWDictionary serialization null check (#6837)
  • 309a495 Bump BenchmarkDotNet from 0.13.2 to 0.13.6 (#6834)
  • 020b29c Bump Microsoft.Data.SQLite from 7.0.8 to 7.0.9 (#6835)
  • c72855b added req/s reporting for macro-benchmarks (#6829)
  • Additional commits viewable in compare view


Dependabot compatibility score

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 commented 1 year ago

CLA assistant check
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] commented 1 year ago

Superseded by #463.