HN user

throwaway3563

102 karma
Posts2
Comments58
View on HN

The most that the ATSB was able to determine was that the data corruption was basically akin to a C++ reinterpret_cast of "altitude" as "angle of attack", causing the 37,000ft or so altitude to sporadically be read as a 50 degree AoA.

The issue was not definitively traced to cosmic rays or another root cause.

“Not happy…” (“Jan”) would probably work for most Aussies, as one of the most well-known but still local catchphrases.

The main issue with powershell is its name. It would have been better named powerscript. It’s not really a shell but a much more powerful script language along the lines of Perl or PHP.

In a similar boat. I was paying $85 a year for a Windows code signing .PFX which is an amount I’m willing to pay for an open-source hobby project.

However $400 a year for a HSM signing certificate is ridiculous and seriously overkill for my project.

The big box discount store (which demands that customers buy in bulk to save money, and because it is so far away from you that you can ONLY visit it once per month) is as much a product of US style suburban sprawl, as car-dependency is.

This website is one big dark pattern and it severely detracts from the article.

- Full screen popover when you scroll to the top

- Useless socialmedia “sharing” toolbar covers the text. Like I really need that stuff close to hand at any moment while reading.

- To downvote “was this article helpful” due to the above, you have to login with social media or create an account. No thanks, if you’re resorting to scummy tactics like the above you’re not getting any of my data.

Had a flaky unit test that would randomly fail with some random Chinese character in the output.

The test was running a log parsing tool against a temporary file that had a pseudo-SQL syntax where you could “select ... from c:\Users\...\temp\abcd1234.xyz\testdata.dat”. The temporary directory was a randomly generated name so that the folder was guaranteed to be empty before every execution of the test.

The test failed on the rare occasion that the randomly generated temp dir consisted of the letter ‘u’ plus four characters that were valid hex digits. When this happened the randomly generated dir name interacted with the backslash before it and become a Unicode escape sequence. It was easy to fix but that test was flaky for months before anyone worked out why.

The write load will be nearly constant but it won’t be sequential. The host device is going to have to update file system data structures periodically as it is writing the video stream; those structures will be at various different places on the drive. So the write load will look like 99% sequential, 1% random. That small amount of random writes in a non-contiguous stream is enough to cause SMR-related rewrite stuttering, especially since with DMSMR the host has no idea how logical blocks presented by the drive map to SMR regions.

Please don’t tell me what not to do, it’s considered harmful.

Especially please don’t tell me to ignore an industry standard only to offer some bespoke solution as an alternative.