Christopher Bradford
Christopher Bradford
Yes, that is what I was thinking.
Any update on this? We're doing a migration from 3.x to 8.x and ran into this same issue. Changing to object is feasible, but has ripple effects through our codebase.
Is this limited to transactions, or does it apply in any case where the default Newtonsoft serializer settings will not work?
After email exchanges with Event Store support, it turns out that the issue was having a readBatchSize greater than the buffer size; configuring the buffer size to be greater than...
So I guess the bug was in Orleans 3.x, which did not deadlock?
I understand the principle and I'm pretty sure the intentions were the same in Orleans 3.x. It just so happened that we had a few places in our Orleans 3.x...
We encountered a related issue with code like this: ```csharp private readonly List _problems = []; public List Problems { get { return _problems; } set { _problems.AddRange(value); } }...
@ReubenBond Yes, this is post-deserialization, and yes, this is surprising behavior 🤣 . I didn't include the serialization attributes in my snippet, but they are there as follows: ```csharp [GenerateSerializer]...
And if we substitute `new()` for `[]`, everything works as expected.
Just discovered that we can also resolve it as follows: ```csharp [GenerateSerializer] [Alias("CommandOutcome")] public record CommandOutcome { [Id(1)] private readonly List _problems = []; ... [Id(0)] public List Problems {...