This... this is the absolute best bug I've come across in the last couple of months. A quick summary.
Show this thread
-
This has worked without fail for the last year or so, but failed today. Well, it didn't actually fail, it just froze, not doing anything: I checked the backend... there were not actually 8 map jobs running.pic.twitter.com/41yG00J56z
Show this thread
This logging makes it look like you have a time.sleep(1) somewhere, plus some other code that takes 1-2 millis to execute
-
-
Correct, but it's not the actual problem (I posted the actual controller code later on).
-
Oh yeah, didn't think I had diagnosed the problem. Just noticed because I'm one of those weirdos who always defines next_update_time to be the end of the next second/minute/whatever, and then time.sleep(next_update_time - http://datetime.now ())
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.