-
Notifications
You must be signed in to change notification settings - Fork 8
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
Custom service crash when deserializing request #27
Comments
Thanks for the report. Yeah the problem is in the |
Perfect, I have tested the PR, and it does indeed fix the issue. Ah, the cast to auto Regarding the array case, would probably be nice to have, but currently i have no such case. |
Great, thanks for testing the PR, I'll merge it then. As for the issue, I'm leaving it open till array case is fixed. |
It seems like I got a similar issue to #12 which i try to wrap my head around.
My custom service looks as followed
a topic type called Stream with the following content
The service using the topic set Stream
Crashes here
Could it be the allocate_message call, when it got one member which contain members with strings?
The text was updated successfully, but these errors were encountered: