SoylentNews is people
SoylentNews
maxwell demon (1608)
Journal of maxwell demon (1608)
Just before, while moderating, I got this enormous error message:
Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error
I have no idea where to properly report this, though. Thus I just put it here and hope that either the right person finds it, or someone who sees it can tell me where to report.
FWIW, apart from that message, everything seemed to be fine (including moderation, reduction of mod points, and no longer being able to moderate after using up my mod points).
(Score: 2) by Sir Finkus on Sunday April 06 2014, @06:44PM
I believe the github page [github.com] is probably the best, or shoot a message to someone on irc. For that particular error [github.com], it looks like it is known and will be fixed shortly. I've gotten it too, and it didn't seem to affect my moderation at all.
Join our Folding@Home team! [stanford.edu]
(Score: 2) by maxwell demon on Sunday April 06 2014, @08:33PM
Thank you.
I have no experience with github (and no account there), so I guess the IRC solution would be best. Also because I like to keep my online identities separate, and who knows if I'll want to get an account on github for another purpose some time in the future. SN has its own IRC, so I can keep my online identity contained on that channel.
Of course with the bug already known (I should have thought of checking that!), I think I don't need to act on this one. But it's good to know for the future.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 2) by xlefay on Monday April 07 2014, @12:31AM
Yes, Github is the best place to check if the bug is known. In case you're not sure (e.g. can't find any) and you don't care to post bugs yourself, your best bet is to put it on IRC.
Also, please be aware, there's also a #dev channel! :)
(Score: 1) by gishzida on Monday April 07 2014, @06:05AM
Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error
+1 (Insightful) Re:Hey, how about a little true in advertising (1123-27190, 0 points left)
Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and
Except it stuttered... and stuttered... and stuttered the choked. BTW some one needs to spell check that error list-- "i" before "e" except after "c":
where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error Internal SAN check blew up checking moderation rights. Please let the powers that be know how and where you recieved this error
Poll:
(Score: 2) by Adrian Harvey on Monday April 07 2014, @09:59PM
I have had this message and assumed it was because I had submitted mods on a stale page - I think I had started reading the story about 3 hours earlier, shut the tablet, gone and done something else, come back and forgotten how old the page was before continuing to mod. My mod points probably expired in between.
(Score: 2) by NCommander on Monday April 07 2014, @10:36PM
It happens when you overmoderate and try to spend too many points. Its a bit of debug code that never showed up to the lameass filter being lame. (I've managed to reproduce it myself).
Still always moving
(Score: 2) by maxwell demon on Tuesday April 08 2014, @06:09AM
Except that for me it already showed while I still had further moderation points left.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 2) by Open4D on Tuesday April 08 2014, @04:19PM
Same for one of the commenters [github.com]