A C++ map can drop a live cache entry. One <= in a comparator is enough. I forced a timestamp tie...
A C++ map can drop a live cache entry. One <= in a comparator is enough. I forced a timestamp tie and watched a key vanish. Would you have caught that in review?
This is a debugging retrospective. It is not a product tour. The artifact is a comparator audit you can run locally.
The symptom
I reconstructed a small TTL cache. Insert looked fine. Lookup looked fine. Unit tests stayed green.
Then two entries shared the same expiry second. One key disappeared. No throw. No log line. Just a hole.
The Problem We Were Actually Solving The treasure hunt engine used a single Redis sorted...
The Problem We Were Actually Solving Our core game loop was: player scans QR → API writes...
A stamp on tools/list is a claim about later reuse. Presence is not proof the next call is...
A backfill is not a default: one nullable timestamp column made an age-based eviction a silent no-op and pinned a funnel metric…
The Problem We Were Actually Solving Our treasure hunt engine at Veltrix was a real-time...
The Problem We Were Actually Solving Our real goal wasnt fancy LLM prompts or real-time...
