Interface Bug which results in MASSIVE data loss

[JoblessLoser]

It's a bit late for halloween but this is a true horror story.

I was struggling with an odd "you have not saved are you sure you want to reload" message that kept popping up in error as I had already saved before reloading (I do not think this is relevant).
I inadvertently managed hit save whilst reloading was taking place (possibly using Command+s possibly using the File->Save menu it was a case of fingers moving faster then brain).
Instead of preventing the two things to happen a the same time it appears the save took place during the reload.

I believe this has resulted in the data being saved in the state it was half loaded in. Erasing catalog membership and possibly other things from all the package information from the most recent years older packages appear to still have catalog membership and completely erasing the content of all manifest files.

I am hoping that I will be able to restore from back up if not I worry that my username might just have become very appropriate.

[hjuutilainen]

Thank you for the issue. I can confirm and reproduce this bug in my test machine. Will fix it for the next release.

MunkiAdmin always creates backups for files before writing anything. You can find these backups in ~/Library/Application Support/MunkiAdmin/manifest backups/ and ~/Library/Application Support/MunkiAdmin/pkgsinfo backups/. As I tested the bug and nuked my repository, I was able to restore all the changed files from backup copies in that directory. Can you check if the original files are there?

[JoblessLoser]

Many thanks for the information, I can confirm I was able to restore using the incremental backups from the ~/Library/Application Support/MunkiAdmin/ folders.

Please let me know if any action is needed on my part to close the ticket (I assume It will be left open and then be closed without my intervention at next update)

Regards,

[hjuutilainen]

Good to hear you were able to restore the files! Let's keep this issue open until I have a release ready with a fix.

[boy412]

We have experienced this issue twice now. Any updates on a fix?