Hacker News Reader

I put myself in this very position with some cache expiration times.

Almost everything in the server-side that is related to times for a particular client uses milliseconds. Of course, redis’s `SETEX` does not. It uses seconds.

The data got quite stale. But, much like this post, other bugs were uncovered and usefully fixed.

View on HN

For some time the redis-py library had the increment and member argument order of ZINCRBY switched from what standard Redis uses. Of course we didn't notice this small difference.

Debugging this was harddd.

They later switched this around, luckily I read the changelog.

Reply on news.ycombinator.com