I've been staring at this long enough that I can plausibly claim to understand how it works. Put this on the pile of "terrible interview questions that I'm sure someone somewhere is getting asked".
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 21 2019
May 17 2019
May 16 2019
I didn't go all the way down the rabbit hole on this, but it's not immediately obvious to me that this is actually relevant to T5378.
May 15 2019
May 14 2019
May 2 2019
May 1 2019
If you min(1, 2, null), you get null.
Apr 29 2019
I have reviewed this exhaustively and can confirm that it's a big file full of SQL ๐
Apr 24 2019
Apr 23 2019
Apr 19 2019
Apr 18 2019
Apr 17 2019
we can cache datasets by chart key very near the display layer
That screenshot produces quite the intense optical effect. I thought I was looking at moirรฉ effect from a cellphone camera.
A half-step might be to just silence "added a commit to" in all cases?
I feel kinda similarly about getting a flurry of "added commit to TXXX" notifications that fire in addition to the "bob closed DXXX" notifications. We don't have the infrastructure to say stuff like "only hide this notification if the same action already generated a separate notification of type foo, do we?
I guess it's not worth cleaning this up and removing the class + DB rows since it's just a no-op now and shouldn't bother anyone.