Perhaps the 84 second burn overflowed the integer (2^6) and was caught by a 2^7s check (127s)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Follow the wormhole through a path of communities !webdev@programming.dev
The tweet you link didn’t indicate that. It said that an engine failure likely caused the overrun, running for 127 seconds instead of the planned 84. Why would something have a 2^7 int size check?
Edit: Quoted
Am I missing something?
There’s further discussion of possible explanations in the replies
Ah I think it’s Twitter’s new thing where you can’t see replies of your not logged in.
Nitter link. This shows replies.