73

Perhaps the 84 second burn overflowed the integer (2^6) and was caught by a 2^7s check (127s)

you are viewing a single comment's thread
view the rest of the comments
[-] IWriteDaCode@programming.dev 12 points 1 year ago* (last edited 1 year ago)

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

The head of Roscosmos Yuri Borisov said that the main cause of the #Luna25 crash was an engine failure. Instead of the planned 84 seconds, he worked 127 seconds.

Am I missing something?

[-] intelati@programming.dev 2 points 1 year ago

There's further discussion of possible explanations in the replies

[-] IWriteDaCode@programming.dev 5 points 1 year ago

Ah I think it's Twitter's new thing where you can't see replies of your not logged in.

[-] TehPers@beehaw.org 3 points 1 year ago

Nitter link. This shows replies.

this post was submitted on 21 Aug 2023
73 points (94.0% liked)

Programming

17314 readers
61 users here now

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!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS