Petabridge.Cmd.Remote 0.8.0-rc2

• .NETStandard 2.0

  • Akka.Remote (>= 1.4.1-rc3)
  • Petabridge.Cmd.Common (>= 0.8.0-rc2)
  • Petabridge.Cmd.Host (>= 0.8.0-rc2)

Petabridge.Cmd v0.8.0-rc1 builds on top of the work of Petabridge.Cmd v0.7.1, but aimed at supporting [the Akka.NET v1.4.1-rc3 implementation of Akka.NET](https://getakka.net/community/whats-new/akkadotnet-v1.4.html).
---
Petabridge.Cmd 0.7.1 introduces some minor bug fixes and updates prior to the release of Akka.NET v1.4.0:
- Fixed bug where all addresses in Akka.Cluster.Sharding `region-stats` appeared to be the address of the local node running the report;
- Upgraded to Akka.NET 1.3.17;
- Added integration test to verify Serilog compatibility for logging steps.
In order for [Akka.Logger.Serilog](https://github.com/akkadotnet/Akka.Logger.Serilog) to work with `Petabridge.Cmd.Host`, the Akka.NET Testkit, [Phobos](https://phobos.petabridge.com/), _or any other component_ you must always call the Serilog logging adapter from your actor code like this in order to use Serilog semantic logging:
```csharp
var log = Context.GetLogger<SerilogLoggingAdapter>(); // correct
log.Info("My boss makes me use {semantic} logging", "semantic"); // serilog semantic logging format
```
If you do the following you will get string formatting errors everywhere:
```csharp
var log = Context.GetLogger(); // INCORRECT
log.Info("My boss makes me use {semantic} logging", "semantic"); // will throw string formatting errors everywhere
```