Posing with a baggie of thoughts and prayers for victims of a typical mass shooting:
http://web.archive.org/web/20210209185752/https://friendlyatheist.patheos.com/2018/02/19/a-gop-congressman-gave-trump-a-literal-bag-of-prayers-after-the-school-shooting/
I don't think it's 'user error' exactly. Maybe when this has occurred, something in the frunk has obstructed the closing of the hood so it almost latched, but the deformed switch is detecting it as closed. I think they might be adjusting the switch sensitivity in software (maybe it uses a Hall effect sensor and a magnet?) so that this almost-closed condition will be reported as just being open.
The only thing I can think of is if the sensor is a hall effect sensor that detects something (the switch?) being depressed by the hood. The sensitivity of the hall effect sensor might be tuneable. They may be able to reduce the sensitivity so it still detects a properly closed hood, but reports an improperly closed hood as open.
It's annoying that the report just says it's fixed in software without explaining how.
I guess the funny thing is that each Git commit is internally just a file. Branches and tags are just links to specific commit files and of course commits link to their parents. If a branch gets deleted or jumped back to a previous commit, the orphaned commits are still left in the filesystem. Various Git actions can trigger a garbage collection, but unless you generate huge diffs, they usually stick around for a really long time. Determining if a commit is orphaned is work that Git usually doesn't bother doing. There's also a reflog that can let you recover lost commits if you make a mistake.
Except PGP is a substring of the 'technically correct' term. It's like someone saying you're playing on your Nintendo - "Um, actually it's a Nintendo 64."
I think Github keeps all the commits of forks in a single pool. So if someone commits a secret to one fork, that commit could be looked up in any of them, even if the one that was committed to was private/is deleted/no references exist to the commit.
The big issue is discovery. If no-one has pulled the leaky commit onto a fork, then the only way to access it is to guess the commit hash. Github makes this easier for you:
What’s more, Ayrey explained, you don’t even need the full identifying hash to access the commit. “If you know the first four characters of the identifier, GitHub will almost auto-complete the rest of the identifier for you,” he said, noting that with just sixty-five thousand possible combinations for those characters, that’s a small enough number to test all the possibilities.
I think all GitHub should do is prune orphaned commits from the auto-suggestion list. If someone grabbed the complete commit ID then they probably grabbed the content already anyway.
@Morphit
@feddit.uk