Closed pirat89 closed 2 years ago
Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergable. If you want to re-run tests or request review, you can use following commands as a comment:
Please open ticket in case you experience technical problem with the CI. (RH internal only)
Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please consider rerunning the CI by commenting leapp-ci build (might require several comments). If the problem persists, contact leapp-infra.
Can one of the admins verify this patch?
I'd say this is the proper fix https://github.com/oamg/leapp/pull/760
Closing it in favor of #760
btw, I am hitting it now in 100% cases on Py3 with dialogs. I have no idea how I passed through it earlier this day when the dialog has been raised. the object is DictProxy
all the time the question is answered.
On Python3 the loaded answer is "sometimes" represented by DictProxy object. In such a case the answer cannot be serialized into the JSON object and storing into the audit db fails with crash.
"sometimes" ==> I have a suspicion the result is different in case the answer is loaded from the answerfile and userchoices file.
See: https://github.com/oamg/leapp-repository/pull/821
Note: This is not a proper fix. I am sending the commit from a train with unstable network.