Reuben Bond

EDIT: I wrote this before seeing your above comment (I'm on my phone, with no PC in sight). gRPC essentially limits outstanding requests to 100 per connection and queues on...

@iamsamcoder thank you for opening the issue. Are you able to find a corresponding error log from where the exception is thrown? If you search your logs for that exception,...

That serialization configuration is the problem here. I suggest you have a custom serialization provider which uses JSON only for types in your assemblies. You can copy the OrleansJsonSerializer or...

I don't like the idea of sticking "Orleans" in front of everything. What other frameworks/libraries do that? You can already distinguish the attributes using a namespace, and that's what namespaces...

> Some attributes (e.g. [NonSerialized]) are likely re-used for compatibility with BinaryFormatter, but is this really desirable to have as the default? We could have an in-built [NonSerizalized] attribute (and...

The main reason for making them configurable was people not wanting to link to any Orleans libraries or being unable to change the library which code is being generated for....

We support this now, in 4.0. We need an explicit test for it, and eventually docs. Let's keep this open until we at least have an explicit test for it

We will add the following property to `SerializationProviderOptions` ``` C# /// /// The to use when logging types serialized by the . /// /// /// The default value is ....

Are you sure it uses recursion and not iteration?

I wonder if you should add a custom serializer for JSON types to fix this, like the one you commented out in your example. The fallback serializer is not supposed...