Bug #806
Ignore list changes lost on crash
0%
Description
Monoclient 0.5-rc1+62 git-64e5ca6
Changes to ignore list lost when crashed on settings change, but other settings changes preserved.
History
#1 Updated by seezer about 15 years ago
- Status changed from New to Rejected
As bad as it may sound, but this won't get "fixed".
Little explanation:
The changes of settings that survived the crash are "local" clientsettings stored in a configfile.
Other settings, like the ignorelist, are fully synchronized settings that get stored in the quasselcore database. This doesn't make much difference for you, as you're running the monolithic client.
Have a look at the wiki if you're interessted in the client/server idea behind quassel.
So pressing "apply" in a settingspage actually might do two things: Either write to local config file or request synchronisation with the core. If your client crashes in between, the core will never know of your changes an thus will not store them.
In regard to your other bugreport #807:
Another point is that the core doesn't write those settings to the database directly as that would make it even slower. So a crashing core can't guarantee that all changed settings get written to disk.
Generally this should be no problem as the crashes are the problem, not the way we treat the writing to the database.
#2 Updated by fen about 15 years ago
To clarify, it's all ignore list changes since the start of the session that are lost, even ones successfully applied before the crash. Also, it appears that the chat buffers for the crashed session are preserved despite the crash. This would suggest that ignore list changes aren't saved till end of session and so are lost in a crash.
#3 Updated by seezer about 15 years ago
You're right. Didn't actually notice that there is a special treatment for bufferviews.
There are a few things not getting periodically stored to disk. Will investigate/fix that.
Thank you for reporting.
Too bad Redmine doesn't allow changing status if it's rejected..