Fix global parameters not persisted when set#232
Conversation
Call prefs.save() from ui_setgroup_global() so that "set global ..." writes updated values to the preferences file. Without this, the change only applied in memory and was lost when the process exited, so a subsequent "get global ..." (e.g. auto_use_daemon) still showed the old value. Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
|
Re-ran the rpm-build and Testing Farm CI tests. The rpm-build eventually succeeded; the previous failure appears to have been a build infrastructure issue rather than a problem with our code. The Testing Farm CI tests failed due to two known issues:
FAILED libiscsi-local.py::TestLibiscsiLocal::test_libiscsi_test_cu[ALL.PrinReadKeys] All other CI tests have passed. This PR should have fixed the global parameter setting issue. |
Call prefs.save() from ui_setgroup_global() so that "set global ..." writes updated values to the preferences file. Without this, the change only applied in memory and was lost when the process exited, so a subsequent "get global ..." (e.g. auto_use_daemon) still showed the old value.