-
Notifications
You must be signed in to change notification settings - Fork 1.1k
v1.3.1 Release PR #3073
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
v1.3.1 Release PR #3073
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes incorrect setting and uses file inclusion for reference.conf
Updated cluster-client article
* Updates and fixes for Akka.IO.UDP * bring back Send ctor + Mono issue workaround
fix 3021 - returned Akka.IO.Tcp semantics to use synchronous write
Also filled in some tests for non-generic IgnoreMessages().
Add TestKitBase.IgnoreMessages<TMsg>
* Improving Support for OSX & Rider * Rider/OSX appears to be less forgiving around the csproj format and requires that the nuget dependencies uses Version and not version. * Updated the build.sh script to only install dotnet once and also to pull down protoc from nuget. * The FAKE build has been updated to support building the Protobuf target on OSX & Linux * Fix the dotnet bootstrapping section, it wasn't setting up environment variables properly if dotnet was already installed.
* Ported over MessageSerializer & SnapshotSerializer from JVM Akka * Custom serializers are now being used as expected. Previously, as is evident by the unit test changes, custom serializers were not being used when serializing Akka.Persistence.IMessage. * LocalSnapshotStore automatically picks up the new serializer and should work better with protobuf based snapshots
Protobuf Serialization for Akka.Persistence.IMessage
…l.Common This addresses #3019 * Added a serializer id to the sql columns * Updated how the manifest is set to support SerializerWithStringManifest * ReadEvent should be backwards compatible
Ensure the serializer uses the default serializer specified.
Correct sample code mistake.
Update quickstart.md
* updated cluster-client docs * Updated other clustering docs to use shorthand config notiation * Updated remote docs Some pages didn't use the shorthand notation consistently
…#3032) * Updating ProtobufSerializer to automatically lookup parser The existing implementation of ProtobufSerializer requires RegisterFileDescriptor to be called with the file descriptor of every protobuf message that will be serialized. This adds a significant amount of boilerplate to serializer protobuf messages automatically. To work around this, I've updated the fromBinary to lookup the MessageParser at runtime based on the type. This brings it inline with how the JVM Akka protobuf serializer works. * Fixing approved remote api
* Protobuf serialization support for FSM types To bring the Akka.Persistence module more in line with the JVM Akka implementation protobuf serialization of PersistentFSMSnapshot and StateChangeEvent classes. As PersistentFSMSnapshot uses generics, reflection is needed to properly serialize and deserialize the class. * Updating Akka.Persistence public api spec. Added a few additional tests around the FSM serialization.
* updated UdpConnection to match TcpConnection send semantics * added specs to cover UdpConnected and fixied UDP connectionless send
* * fixed issue with DNS resolution on outbound TCP connections * added IPV6 support to TCP sockets on Akka.IO * added IFDEF to disable IPV6 testing on non-Windows systems * still run DNS resolution for IPV4 on .NET Core Linux
* Updated PersistenceMessageSerializer * fix api
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1.3.1 September 5 2017
Maintenance Release for Akka.NET 1.3
Updates and bugfixes:
ByteString
payload had buffers with length more than 1,UdpSender
only wrote the first part of the buffers and dropped the rest.SerializerWithStringManifest
required by Akka.Cluster.Sharding and Akka.Cluster.ToolsSerializerWithStringManifest
, so using Akka.Cluster.Sharding with Sql plugins would not work.PersistenceMessageSerializer
was failing with the wrong exceptoin when a non-supported type was provided.Akka.Persistence backwards compability warning:
SerializerWithStringManifest
calledserializer_id
. It requires any previous Sql schema to be updated to have this field. Details are included in the Akka.Persistence.Sqlite plugin README.md file. Users of the Akka.Persistence.Sqlite plugin must alter their existing databases to add the fieldserializer_id int (4)
:See the full set of Akka.NET 1.3.1 fixes here.