Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Daniel Frederico Lins Leite
    @xunilrj
    SomeBank.Accounts.Domain+RecordWithString
    SomeBank.Accounts.Domain+RecordWithMap
    System.Collections.DictionaryEntry
    System.Object
    Bartosz Sypytkowski
    @Horusiath
    @xunilrj I think, I know what's going on - it's the crap with F# lazy eval for identifiers declared directly in modules
    this can be reason why the serializer isn't working
    Roger Johansson
    @rogeralsing
    I've implemented the F# Map serializer now. everything is passing
    Bartosz Sypytkowski
    @Horusiath
    @rogeralsing I'm not sure if map serializer was the problem, it looks more like a very specific case of the code that @xunilrj used
    Roger Johansson
    @rogeralsing
    it was, because the execution path ended up in the generic dict serializer, which wasnt implemented
    at least for the code he provided
    var r2 = SomeBank.Accounts.Domain.createRecordWithMap;
    s.Serialize(r2, mem); //this throws the exception below
    This now works
    Daniel Frederico Lins Leite
    @xunilrj
    thanks!
    Bartosz Sypytkowski
    @Horusiath
    I've rebased the latest Wire from AsynkronIT and I'm getting an exception when trying to build a Wire.csproj: Your project is not referencing the ".NETFramework,Version=v4.5" framework. Add a reference to ".NETFramework,Version=v4.5" in the "frameworks" section of your project.json, and then re-run NuGet restore
    I think, that Wire.project.json is messing here
    Roger Johansson
    @rogeralsing
    @Horusiath ok, Ill get on that
    Btw, the internal messages in Akka is hard to test, only way is via reflection atm.
    internal as using the internal modifier
    pikulearns
    @pikulearns
    Hi..I'm an akka.net newbie. I upgraded the serializer to Wire in my project and when serialising an object with an ImmutableList, serialisation does not work.
    If I change it to List it works perfectly fine. Any suggestions?
    Error [Object of type 'XYZ.SerialiseCompleted1[System.String][]' cannot be converted to type 'System.Collections.Generic.IEnumerable1[System.String]'.] [ at System.RuntimeType.TryChangeType(Object value, Binder binder, CultureInfo culture, Boolean needsSpecialCast) at System.RuntimeType.CheckValue(Object value, Binder binder, CultureInfo culture, BindingFlags invokeAttr) at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig) at System.Reflection.RuntimeMethodInfo.InvokeArgumentsCheck(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters) at Wire.SerializerFactories.ImmutableCollectionsSerializerFactory.<>cDisplayClass5_0.<BuildSerializer>b1(Stream stream, DeserializerSession session) at Wire.ValueSerializers.ObjectSerializer.ReadValue(Stream stream, DeserializerSession session) at Wire.StreamExtensions.ReadObject
    pikulearns
    @pikulearns
    Akka.Serialization.Wire:1.1.2.30 beta
    Akka.NET: 1.1.2
    pikulearns
    @pikulearns
    @rogeralsing : Any suggestions for the Wire serialisation issue for an ImmutableList
    Reuben Bond
    @ReubenBond
    Is this also the Hyperion room?
    I'm curious about a few things:
    1. How robust is version-tolerance support? It seems like it's not implemented
    2. Why is all of the IL code conditionally compiled for NET45 only? I would expect that the entire project moves to IL, since LINQ Expressions are too limited
    Aaron Stannard
    @Aaronontheweb
    @ReubenBond we probably need to set a new one up for Hyperion
    onto the second question, you mean it's not emitted for .NET Standard target? cc @alexvaluyskiy
    Reuben Bond
    @ReubenBond
    it's surrounded by #if NET45
    and the first q?
    Aaron Stannard
    @Aaronontheweb
    right now it reads like a TODO: impement
    so I don't think it's been implemented
    we'll be clearer on that before we switch it to the default for Akka.NET
    either it'll be implemented or not given as an option
    Reuben Bond
    @ReubenBond
    thanks, @Aaronontheweb :)
    Alex Valuyskiy
    @alexvaluyskiy
    Should we check for NonSerializedAttribute on every class, even if it is not have a SerializableAttribute?
    Bartosz Sypytkowski
    @Horusiath
    It's only called once per type, also I think it's not a problem to have it
    Phil Sandler
    @philsandler_twitter
    I just posted a question to the mailing list, but I'll ask one part of it here as well
    Hyperion is still in beta. How stable is it? Can we confidently use it in production?
    (As an aside, what is the relationship between Hyperion and Wire? I thought they were the same)
    Aaron Stannard
    @Aaronontheweb
    Hyperion is going to undergo some changes
    can't make any promises about wire format
    it's absolutely necessary though to run some of our built-in modules right now
    can't use sharding without it
    once Hyperion 1.0
    comes out, we'll be versioning the wire format more carefully
    Phil Sandler
    @philsandler_twitter
    so recommended to stick with json for now?
    Aaron Stannard
    @Aaronontheweb
    I would if I didn't depend on Cluster.Ddata or Cluster.Sharding
    the JSON.NET stuff is stable but it has much worse performance
    like 25x worse
    Phil Sandler
    @philsandler_twitter
    we don't so I think we'll stick with json. As noted in the mailing list post, it can't deserialize the Failure type
    performance shouldn't be a big concern at this point
    Thanks for your help!
    Phil Sandler
    @philsandler_twitter
    looks like (de)serializing exceptions is a know issue: akkadotnet/akka.net#1886