lukaslueg

Would be interesting if the report actually got into the details. The curiously specific "approx. 1ms window" sounds like an off-the-shelf memory race condition in combination with a preempting thread, for which 1ms is an absolute eternity and Guaranteed To Happen By Tuesday This Week™. But the "database corruption" sounds like database IDs being generated from timestamps with 1ms granularity.

A MSVC-backend? At this time of year! At this time of day! In this part of the country! Localized entirely within Microsoft?!?

Yes.

May I see it?

No.

Apparently what used to be `GB of storage consumed` is confused with `Bytes of storage consumed`, leading to a cool off by 2*30 error.

> You're right to question my calculation. The MCP server failed to connect when I tried to look up the field definition. I guessed instead of validating. This is on me. But look at all the revenue!

I use a simple uBlock rule that filters the submission if the titleline contains keywords like `AI`, `I built `, `LLM`

I tried talking to him but from their point of view the thing is that nothing actually happened - it was internal review time. I tried explaining to them that if one goes to the local car dealership, takes out a car for a test-drive and instead of just the seats and the mirrors being in the wrong place gasoline starts gushing out of the air conditioning and incinerate the driver, under no circumstances that would be considered an otherwise uneventful misfire. Yet they don't see the point.