"Testing this shit" -> We’ve found 129,140 code results
https://github.com/search?utf8=%E2%9C%93&q=Testing+this+shit...
This should never happen
91–100 of 214 posts
Re: This should never happen
#92My favorite part is the Java project that has an exception class called ThisShouldNeverHappenException [1]. Only in Java would someone create an exception class for a condition that should never happen :) [1] https://github.com/TheProjecter/propidle/blob/f0d5320e2a3d46...
Why man has nipples if he does not breast feed?
I could ask you the very same question.
Re: This should never happen
#93Reminds me of the "Six Stages of Debugging": http://plasmasturm.org/log/6debug/
Re: This should never happen
#94My favorite example of a "this should never happen" error was when I got a call from a customer, who started the conversation by asking, "Who is Brian?".
I was caught a bit off guard, but I assumed the customer must know someone at the company, since Brian was the name of the previous electrical engineer/firmware programmer. So, I told them that Brian didn't work here any more, but was there anything that I could help them with? The customer said, "Well, the device says that I should call Brian". I was confused by this, and asked a lot of questions until I determined that the device was actually displaying "CALL BRIAN" on the LCD display.
This was quite unusual, and at first I didn't believe the customer, until he sent a picture of the device showing the message.
So, I dug into the code, and quickly found the "Call Brian" error condition. It was definitely one of those "this should never happen" cases. I presume that Brian had put that in during firmware development to catch an error case he was afraid might happen due to overwriting valid memory locations.
I got the device back, and found out that the device had a processor problem (I don't remember exactly what) that would write corrupted data to memory. So, really, it should never happen.
That particular device has now been in production for 10 years, and that is the only time that error has ever appeared.
Re: This should never happen
#95Earlier quoted context omitted.
It's a sub-pattern of "ain't got time for dat". Developer knows that condition should never happen, but is not inclined to prove it (as represented by coding type checking or other handling) yet realizes it shouldn't be ignored outright (if only to document the unproven condition in code, or to shut the compiler up about incompleteness warnings).
It's also for cases when you know it can't happen. For example, Java's String class has a method public byte[] getBytes(String charsetName) throws UnsupportedEncodingException Since it can throw a checked exception you have to catch it, which generally is fine, but consider this case: someString.getBytes("UTF-8"); This call can never fail (support for UTF-8 encoding is required in Java) but in my case I have to do so…
FWIW getBytes(Charset) doesn't throw, and there's a base set of charsets in StandardCharsets (1.7+):
someString.getBytes(StandardCharsets.UTF_8);
Re: This should never happen
#96This is awesome.
public class ThisShouldNeverHappenException extends RuntimeException {
public ThisShouldNeverHappenException(Exception cause) {
super(cause);
}
}Re: This should never happen
#97Earlier quoted context omitted.
HyperLogLog[1] will do that. You can find it in Redis, Lucene; and I suspect it is also hidden behind BigQuery's count(distinct X)s. [1] https://en.wikipedia.org/wiki/HyperLogLog
What part of the algorithm would cause the number to change significantly every time you run the query?
All shards compute their own, and send the result in a non deterministic order. My explanation is that the merge part of HLL depends on the order.
Line 95 of this method [1] from this implementation [2] shows a max(mask(x), mask(y)), which is not associative but is a close proxy to max()(which is associative).
[1] https://github.com/addthis/stream-lib/blob/af045cb4199959c07...
[2] https://github.com/addthis/stream-lib/blob/master/src/main/j...
Re: This should never happen
#98[deleted]
Re: This should never happen
#99Using github to search like this reminds me of how a CS professor of mine would show the "best commit messages of the year" (homework was submitted via git) by looking for various patterns like all caps, all symbols, etc. http://www.slideshare.net/bsotomay/uchicago-cmsc-23300-the-b...
My favorite commit message of all time:
https://core.trac.wordpress.org/changeset/26851
---
The Pinking Shears stir from their slumber, awakened by what may seem, to those innocent in the ways of The Shears, a triviality, a nothing-of-consequence. But there are consequences indeed for recklessly trailing your whitespace. Naturally, they a dire!
One, two! One, two! And through and through
The Pinking Shears went snicker-snack!
They plucked your tail and with your space
They went sniksnuking back.
Let me tell you, that can be uncomfortable, so always pre-sniksnuk your trailing whites. May The Shears be with you.
Re: This should never happen
#100My favorite example of a "this should never happen" error was when I got a call from a customer, who started the conversation by asking, "Who is Brian?". I was caught a bit off guard, but I assumed the customer must know someone at the company, since Brian was the name of the previous electrical engineer/firmware programmer. So, I told them that Brian didn't work here any more, but was there anything that I could hel…
Did you tell brian?