-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
Inifinite loop in the DateTime resolvers. #463
Comments
I think the easy solution is to check if the resolver is derived from the DefaultContractResolver to prevent the re-entry. I won't realistically get it to later this week so if you get a PR in before then I will merge as soon as I see it. |
should be resolved in #465 I can't reproduce the loop in unit tests. but i can in the real app (randomly -often enough- though). |
Plz merge and post nuget as soon as you can, its very urgent ;) |
Hey 👋, We saw you use our package. To keep our code as accessible as possible, we decided to open source it and are now helping others with their questions. In a pursuit to continue our work, help us by donating to our collective! ❤️ https://opencollective.com/reactiveui
|
My pr introduced a bug showing an infinite loop of calls exhausting the stack:
edit: it's not my pr, it's your code lol :)
edit2: it's not my pr, it's not your code. It's when an existingContractResolver is non null and derives from DefaultContractResolver. Then it loops ...
Originally posted by @softlion in #459 (comment)
The text was updated successfully, but these errors were encountered: