-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Regression: StackOverflowError
with recursive types that contain Map.Entry
#938
Comments
Maybe be better if we comment the issue here, not on the gist 👍 |
@jloisel haven't had time to dig into this yet. It does seem odd that there is discrepancy here. |
I'm going to try to isolate it further too. If i find something i'll let you know here. |
I isolated the bug a bit more: It seems like it's related to the implemented interfaces which reference the type itself. I removed all external dependencies. |
Thanks. There are known open issues wrt resolution of recursive type definitions (oldest open being #76 I think). What is odd is rather that this would surface between 2.5 and 2.6; not its existence. |
StackOverflowError
with recursive types that contain Map.Entry
I think I know which change triggered the problem; I was also able to change code to work for the test case that resolves type; although now that I write this I realized I need to go back and verify that actual deserialization also works, just to be sure. |
Hi,
I encounter the following issue with 2.6.x (works fine with 2.5.4):
The JUnit which shows how to reproduce the error:
https://gist.github.com/jloisel/1d36c017f5b27617c27b
The text was updated successfully, but these errors were encountered: