petabridge / Akka.Persistence.Azure

Azure-powered Akka.Persistence for Akka.NET actors
Apache License 2.0
13 stars 11 forks source link

Bump AkkaHostingVersion from 1.5.20 to 1.5.24 #406

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps AkkaHostingVersion from 1.5.20 to 1.5.24. Updates Akka.Persistence.Hosting from 1.5.20 to 1.5.24

Release notes

Sourced from Akka.Persistence.Hosting's releases.

1.5.24

Update Akka.NET to 1.5.24Add ShardedDaemonProcess integration You can now start ShardedDaemonProcess host and proxy using Akka.Hosting through 2 new Akka.Cluster.Hosting extension methods csharp public static AkkaConfigurationBuilder WithShardedDaemonProcess( this AkkaConfigurationBuilder builder%2C string name%2C int numberOfInstances%2C Func entityPropsFactory%2C ClusterDaemonOptions? options = null)

csharp public static AkkaConfigurationBuilder WithShardedDaemonProcessProxy( this AkkaConfigurationBuilder builder%2C string name%2C int numberOfInstances%2C string role)

Akka.Hosting v1.5.22

Update Akka.NET to 1.5.22Add log filtering extension method Filtering Logs In Akka.NET In Akka.NET 1.5.21%2C we introduced log filtering for log messages based on the LogSource or the content of a log message. Depending on your coding style%2C you can use this feature in Akka.Hosting in several ways.

  1. Using The LoggerConfigBuilder.WithLogFilter() method.

The LoggerConfigBuilder.WithLogFilter() method lets you set up the LogFilterBuilder

   builder.Services.AddAkka("MyActorSystem"%2C configurationBuilder =>
   {
       configurationBuilder
           .ConfigureLoggers(loggerConfigBuilder =>
           {
               loggerConfigBuilder.WithLogFilter(filterBuilder =>
               {
                   filterBuilder.ExcludeMessageContaining("Test")%3B
               })
           }
   })
  1. Setting the loggerConfigBuilder.LogFilterBuilder property directly.
   builder.Services.AddAkka("MyActorSystem"%2C configurationBuilder =>
   {
       configurationBuilder
           .ConfigureLoggers(loggerConfigBuilder =>
</tr></table> 

... (truncated)

Changelog

Sourced from Akka.Persistence.Hosting's changelog.

[1.5.24] / 10 June 2024

You can now start ShardedDaemonProcess host and proxy using Akka.Hosting through 2 new Akka.Cluster.Hosting extension methods

public static AkkaConfigurationBuilder WithShardedDaemonProcess<TKey>(
   this AkkaConfigurationBuilder builder,
   string name,
   int numberOfInstances,
   Func<ActorSystem, IActorRegistry, IDependencyResolver, Func<int, Props>> entityPropsFactory,
   ClusterDaemonOptions? options = null)
public static AkkaConfigurationBuilder WithShardedDaemonProcessProxy<TKey>(
   this AkkaConfigurationBuilder builder,
   string name,
   int numberOfInstances,
   string role)

[1.5.22] / 4 June 2024

Filtering Logs In Akka.NET

In Akka.NET 1.5.21, we introduced log filtering for log messages based on the LogSource or the content of a log message. Depending on your coding style, you can use this feature in Akka.Hosting in several ways.

  1. Using The LoggerConfigBuilder.WithLogFilter() method.

    The LoggerConfigBuilder.WithLogFilter() method lets you set up the LogFilterBuilder

    builder.Services.AddAkka("MyActorSystem", configurationBuilder =>
    {
        configurationBuilder
            .ConfigureLoggers(loggerConfigBuilder =>
            {
                loggerConfigBuilder.WithLogFilter(filterBuilder =>
                {
                    filterBuilder.ExcludeMessageContaining("Test");
                });
            });
    });
    

... (truncated)

Commits


Updates Akka.Cluster.Hosting from 1.5.20 to 1.5.24

Release notes

Sourced from Akka.Cluster.Hosting's releases.

1.5.24

Update Akka.NET to 1.5.24Add ShardedDaemonProcess integration You can now start ShardedDaemonProcess host and proxy using Akka.Hosting through 2 new Akka.Cluster.Hosting extension methods csharp public static AkkaConfigurationBuilder WithShardedDaemonProcess( this AkkaConfigurationBuilder builder%2C string name%2C int numberOfInstances%2C Func entityPropsFactory%2C ClusterDaemonOptions? options = null)

csharp public static AkkaConfigurationBuilder WithShardedDaemonProcessProxy( this AkkaConfigurationBuilder builder%2C string name%2C int numberOfInstances%2C string role)

Akka.Hosting v1.5.22

Update Akka.NET to 1.5.22Add log filtering extension method Filtering Logs In Akka.NET In Akka.NET 1.5.21%2C we introduced log filtering for log messages based on the LogSource or the content of a log message. Depending on your coding style%2C you can use this feature in Akka.Hosting in several ways.

  1. Using The LoggerConfigBuilder.WithLogFilter() method.

The LoggerConfigBuilder.WithLogFilter() method lets you set up the LogFilterBuilder

   builder.Services.AddAkka("MyActorSystem"%2C configurationBuilder =>
   {
       configurationBuilder
           .ConfigureLoggers(loggerConfigBuilder =>
           {
               loggerConfigBuilder.WithLogFilter(filterBuilder =>
               {
                   filterBuilder.ExcludeMessageContaining("Test")%3B
               })
           }
   })
  1. Setting the loggerConfigBuilder.LogFilterBuilder property directly.
   builder.Services.AddAkka("MyActorSystem"%2C configurationBuilder =>
   {
       configurationBuilder
           .ConfigureLoggers(loggerConfigBuilder =>
</tr></table> 

... (truncated)

Changelog

Sourced from Akka.Cluster.Hosting's changelog.

[1.5.24] / 10 June 2024

You can now start ShardedDaemonProcess host and proxy using Akka.Hosting through 2 new Akka.Cluster.Hosting extension methods

public static AkkaConfigurationBuilder WithShardedDaemonProcess<TKey>(
   this AkkaConfigurationBuilder builder,
   string name,
   int numberOfInstances,
   Func<ActorSystem, IActorRegistry, IDependencyResolver, Func<int, Props>> entityPropsFactory,
   ClusterDaemonOptions? options = null)
public static AkkaConfigurationBuilder WithShardedDaemonProcessProxy<TKey>(
   this AkkaConfigurationBuilder builder,
   string name,
   int numberOfInstances,
   string role)

[1.5.22] / 4 June 2024

Filtering Logs In Akka.NET

In Akka.NET 1.5.21, we introduced log filtering for log messages based on the LogSource or the content of a log message. Depending on your coding style, you can use this feature in Akka.Hosting in several ways.

  1. Using The LoggerConfigBuilder.WithLogFilter() method.

    The LoggerConfigBuilder.WithLogFilter() method lets you set up the LogFilterBuilder

    builder.Services.AddAkka("MyActorSystem", configurationBuilder =>
    {
        configurationBuilder
            .ConfigureLoggers(loggerConfigBuilder =>
            {
                loggerConfigBuilder.WithLogFilter(filterBuilder =>
                {
                    filterBuilder.ExcludeMessageContaining("Test");
                });
            });
    });
    

... (truncated)

Commits


Updates Akka.Cluster.Sharding from 1.5.20 to 1.5.24

Release notes

Sourced from Akka.Cluster.Sharding's releases.

Akka.NET v1.5.24

1.5.24 June 7th 2024

Akka.NET v1.5.24 is a patch release for Akka.NET that addresses CVE-2018-8292 and also adds a quality of life improvement to IActorRef serialization.

COMMITS LOC+ LOC- AUTHOR
3 35 22 Gregorius Soedharmo
1 26 51 Mike Perrin
1 15 2 Aaron Stannard

You can see the full set of changes for Akka.NET v1.5.24 here.

  • 052277953a80ef8fb529af9f5ae94e19cc466dd8 Update RELEASE_NOTES.md for 1.5.24 release (#7239)
  • 525a282227b721d3c47fc6c3c6ecfa3301b184e0 Partial fix on CVE-2018-8292 (#7238)
  • e144c5dd2019319e2055b3976191048c85669ab0 Added Serialization.DeserializeActorRef method (#7237)
  • 79f9bc64ece88199781d1f9b0fe11be078c9c678 Fix serialize-messages=on DeadLetter inside DeadLetter bug (#7236)
  • 3c61f462906e8e4ab31a6f11ec734aa85b9d6caa Partial fix for CVE-2018-8292 (#7235)
  • 64a71b85bfc30ee9aff0613a86b466a618908e37 Tidied up the language on Fault Tolerance page (#7232)

This list of changes was auto generated.

Akka.NET v1.5.23

1.5.23 June 4th 2024

COMMITS LOC+ LOC- AUTHOR
2 299 44 Aaron Stannard
1 47 49 Gregorius Soedharmo
1 1 1 Hassan Abu Bakar

You can see the full set of changes for Akka.NET v1.5.23 here.

Changes:

  • 2dfbecfcde5bea24020aecf8207354e93083f2f9 Update RELEASE_NOTES.md for 1.5.23 (#7233)
  • efaea2df269a63776d8aff1c61335590addb7f4a ShardedDaemonProcess push mode (#7229) [ #7195 ]
  • 356c91145dc353a002663d0ec479db8dc3adbc3e Change from Gitter to Discord (#7231)
  • 5a2818f44b811dbfd20d3a093ce757c2db53930d Fix missing HandOverDone handler in ClusterSingletonManager (#7230)
  • 7747a68303c7455e0e3b103aba572e66e802356b Added v1.5.23 placeholder (#7227)

This list of changes was auto generated.

... (truncated)

Changelog

Sourced from Akka.Cluster.Sharding's changelog.

1.5.24 June 7th 2024

Akka.NET v1.5.24 is a patch release for Akka.NET that addresses CVE-2018-8292 and also adds a quality of life improvement to IActorRef serialization.

COMMITS LOC+ LOC- AUTHOR
3 35 22 Gregorius Soedharmo
1 26 51 Mike Perrin
1 15 2 Aaron Stannard

You can see the full set of changes for Akka.NET v1.5.24 here.

1.5.23 June 4th 2024

COMMITS LOC+ LOC- AUTHOR
2 299 44 Aaron Stannard
1 47 49 Gregorius Soedharmo
1 1 1 Hassan Abu Bakar

You can see the full set of changes for Akka.NET v1.5.23 here.

1.5.22 June 4th 2024

Akka.NET v1.5.22 is a patch release for Akka.NET with a few bug fixes and logging improvement.

On Resolving CVE-2018-8292

In order to resolve this CVE, we had to update DotNetty.Handlers to the latest version and unfortunately, this comes with about 10% network throughput performance hit. We are looking into possible replacement for DotNetty to improve this performance lost in the future (see [#7225](https://github.com/akkadotnet/akka.net/issues/7225) for updates).

Before

Num clients, Total [msg], Msgs/sec, Total [ms], Start Threads, End Threads  
         1,  200000,    125000,    1600.62,            46,              76  
         5, 1000000,    494072,    2024.04,            84,              95  
        10, 2000000,    713013,    2805.73,           103,             107  
</tr></table> 

... (truncated)

Commits


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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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[bot] commented 4 months ago

Superseded by #409.