WHY THE FUCKETY FIDGETS DOES THIS ERROR HAPPEN ONLY ONE FOURTH THE TIME?!?!

What's really okay with the rest 75%, huh?
I'm losing my sanity.

@Demolishun So theoretically... the error can only happen 3.2% of times at best... I wish I hadn't used the datetime library D:

sounds like multithreading honestly,
or maybe something regarding negative time comparisons.

One can only guess, since the description of the problem is rather lacking

I second @thebiochemic 's opinion here.

- Check for synchronization and concurrency errors.

- Also make sure you're not using any calls to get random numbers anywhere in the code, and if you do, check that all the conditions are in-bound

- Also make sure you're closing all your files and sockets if any, sometimes you can flood the system with open descriptors and that can cause some fuckery

Without knowing more about the problem in particular I guess that's the best tips I can offer :D hope it helps in some way

@thebiochemic The code is single threaded about veginere ciphers. I ended up rewriting it.

It mysteriously disappeared. God knows why

I'd be lying if I said there was likely a portion of the cause you can't reproduce or is simply not occurring

Network related ?