3 ms·
The question is whether this is code that's special for crashes, or code that runs the exact same way for all data uploads, regardless of whether there's a cras
by Thorrez 1y ago
The question is whether this is code that's special for crashes, or code that runs the exact same way for all data uploads, regardless of whether there's a crash.
You're implying it's special for crashes, but we don't know that.
- lexicality 1y agoThe crash system uses this code, therefore they chose to do something that would delete the crash data after a crash. Saying "hey, the upload_and_delete function is used in loads of places!" doesn't free you of the responsibility that you used that function in the crash handler.
- Thorrez 1y agoIs this a crash handler, or is it their normal telemetry upload loop?
- lexicality 1y agoYes, it's a crash handler that uploads a blackbox "collision snapshot" of the entire car's state leading up to a crash. It's very well documented that Tesla does this, including in the article.
- dylan604 1y agoYou have it backwards. The fact that after the special condition of a crash it still allows the data to be deleted is an issue. Sure, deleting of normal data is fine, but it clearly detected a crash and did not mark the file in the special crash mode as do not delete is mind boggling. Everyone knows that in a crash detection mode that the data is very important. Not having code to ensure data retention is the laziest at best way of doing things or malevolently designed at worst. Tesla and its leadership do not deserve at best as our default choice.
- sim7c00 1y agoif its not special for crashes thats criminally bad design in a safety critical system. u know if for instance u weld a gas pipeline and an xray machine reveal a crack in your work, you can go to jail.... but if you treat car software as an appstore item, totally fine?? stop defending ridiculously bad design and corporate practices.