-
Notifications
You must be signed in to change notification settings - Fork 41
-
Notifications
You must be signed in to change notification settings - Fork 41
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
RecursionError: maximum recursion depth exceeded while calling a Python object #16
Comments
Thanks @besser82 i'll look at it |
As i wrote it the original report, i cannot reproduce it atm. If someone can do it in vm, maybe saving a rollback position to test the case more times... or help me to find a way... |
Looking at the last comment in rhbz this might be related to the Gtk-backend… It looks suspicious to me, there is the same backtrace in #18 (comment). |
Not an issue with dnfdragora-code, but libyui-gtk: see rhbz. |
Temporary fix in cca9412. Leaving open to track… |
Even fixing the GTK3-warnings in libyui-gtk (libyui/libyui-gtk@3c7aad0) didn't fix this issue… sigh :( |
could you please test the following patch to see if the crash still occurs? I tried this patch with the old dnfdragora without your max recursion changes and without libyui-gtk changes too, and it worked. I'll test with qt to see if we have no regressions there too |
Test worked fine, when in a transaction with 1161 items (updating Fedora 25 Cinnamon Live with all recent updates available). I used the unfixed libyui-gtk and removed the increase of recursion-depth in Python. Thanks for fixing this issue. =) |
This reverts commit cca9412.
Fixed in 0d6ff95. |
See: https://bugzilla.redhat.com/show_bug.cgi?id=1436451
The text was updated successfully, but these errors were encountered: