Re^2: Errors in Worst Nodes

The technical explanation isn't much different. Server hiccups. MySQL glitches. Xmsn errors. Power dips. Flaky RAM. Disk errors....

There would have to be quite a few of them -- I've been seeing it almost daily.

A "page refresh" may yield the (apparent) result of clearing the error, but it doesn't have much to do with the underlying problem(s).

I know, I just had to take the Microsoft way(where restarting makes problems go away, but then refresh here), as there's not much I could do at the moment.

~Thomas~
confess( "I offer no guarantees on my code." );

Comment on Re^2: Errors in Worst Nodes Download Code

Replies are listed 'Best First'.
Re^3: Errors in Worst Nodes by ww (Archbishop) on Jun 30, 2012 at 20:00 UTC
Yes, sometimes there are an annoying, troublesome, puzzling "quite a few" of them but, OTOH, the annoying, troublesome, puzzling "quite a few" of them could all get thrown because a single adverse occurance is repeating itself. In any case, the keepers of the Monastery are aware... and are using their stockpile of (name your favorite insecticide) to try to stop any further repetitions. Thanks for your concern. Wish I had happier answer.	[reply]
Re^4: Errors in Worst Nodes by Anonymous Monk on Jun 30, 2012 at 22:28 UTC
It better not be toxic to oysters.	[reply]
Re^5: Errors in Worst Nodes by CountZero (Bishop) on Jul 01, 2012 at 11:34 UTC
Oysters??? CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics	[reply]
Re^6: Errors in Worst Nodes by frozenwithjoy (Priest) on Jul 01, 2012 at 11:39 UTC
Re^7: Errors in Worst Nodes by CountZero (Bishop) on Jul 01, 2012 at 21:33 UTC


XP is just a number
	PerlMonks