The following users had their user settings (and a few other things that are stored in the same database field) corrupted and then restored from backup (that was made about 22 hours prior):
Anonymous Monk, cbraga, tye, PotPieMan, theorbtwo,
tilly, graff, jZed, atcroft, thospel,
Zaxo, kiat, FoxtrotUniform, Flame, jryan,
thepen, sulfericacid, hsinclai, rattusillegitimus, Enlil,
leriksen, diotalevi, pg, castaway, edan,
im2, exussum0, Moriarty, phenom, cyclist38,
TilRMan, jcoxen, valentin, matija, Errto,
dimar, Ponky, lwanderi, neilh, perlcapt,
erix, and pip9ball.
Changes to their settings during that day were lost (most likely things like additions to the personal nodelet -- note that scratchpads were not affected). Their counts of write-ups on their home nodes will not reflect nodes posted during that period but anyone may click the "submit" button at user settings to update their own write-up count (which drifts off from accurate due to race conditions in the Everything engine). The first time the XP nodelet was displayed after the backed-up settings were restored, it displayed the XP change relative to the time of the back-up.
Before settings were restored, the corrupted settings were backed-up. So, in the very unlikely event of one of the above people having made a very important settings change for which they are having great difficulty reconstructing said change, an attempt can be made to pull the information out of the corrupted value by hand.
I apologize for the inconvenience. I'd wanted to post this sooner after the event, but sleep got the better of me.
| [reply] |
Thanks tye, i was too tired to get into this level of detail.
Also may I say that while this was a bit disappointing for me in that the first patch to a PM module that ive worked on caused so much trouble. On the other hand I thought we worked well together analyzing and resolving the trouble. So thanks for very much for being there. Next time hopefully things will go a lot more smoothly.
| [reply] |
