-
Notifications
You must be signed in to change notification settings - Fork 2
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
Problem with unmarshaling #15
Comments
@gchudnov To clarify, is this a new issue due to pekko migration or has it always existed (i.e. with akka-streams-json that uses akka)? |
yes, after migration.
and after migration:
it must be affected some Unmarshal[.] operations. |
What versions of akka/akka-streams-json were you using before? |
2.6.20 |
And the akka-streams-json version? |
sorry, missed somehow in the question above :( |
Thanks, ill do my best to try and look into it this week |
@gchudnov I don't think I have time to look into it this week, if you want to pick up the issue then feel free to do so |
The problem with using |
Maybe that explains it, because this issue did not occur in earlier versions of akka-streams, likely 2.5 which behaved differently wrt stream cancellation. |
I am going to close this issue as its a user error (i.e. an unhandled exception via |
No, this is a bug in this library. |
Oh woops, I thought the code was internal and not this library. Re-opening and fixing now. |
@gchudnov Incase you are still using pekko-streams-circe, this issue has been resolved in version 1.1.0 which was just released (see https://github.com/mdedetrich/pekko-streams-circe/releases/tag/v1.1.0) |
@mdedetrich |
Hi @mdedetrich ,
it seems there is a problem in unmarshalling
JsonSupport.scala#L36
and, for example:
main/scala/org/zalando/kanadi/api/Subscriptions.scala#L569-L570 { NOTE: the master-branch is still akka, to the point was migrating to pekko / building only locally }
never produces the result and never completes.
--
but if run manually, e.g.
and then decoding,
there are no issues.
Guess it depends how the response is chunked and it might be not enough data in the
.head
.The text was updated successfully, but these errors were encountered: