[tropshop]

Some time ago I dealt with this exact bug for an e-commerce site with millions of requests per day, and it was also Rails + Unicorn.

ANY time ruby 1.8 raised a timeout, it was silently swallowed, and Unicorn returned the adjacent request session_id. We had to constantly defend against any code that might hit the native timeout.

[artursapek]

Lmao I am so glad Ruby/Unicorn/Rails are a distant memory in my career at this point. So much magic and poorly defined behavior

[imtringued]

I don't write Ruby applications but I have never heard anything good about Unicorn.