You had a problem with your tests being too damn long. You DRY'd them up by using helpers. Now you have two problems.
Stranger Things
"I'm Dorothy Gale from Kansas"
he wasn't even looking at me and he found me
TVSTRANGERTHINGS
I'd rather be in outer space 🛸

ellievsbear
we're not kids anymore.

#extradirty
PUT YOUR BEARD IN MY MOUTH
🪼

⁂
will byers stan first human second
One Nice Bug Per Day
Misplaced Lens Cap
Xuebing Du

Andulka
trying on a metaphor
Lint Roller? I Barely Know Her

❣ Chile in a Photography ❣
$LAYYYTER

seen from T1
seen from United Kingdom

seen from T1
seen from India
seen from United States
seen from United States

seen from France

seen from United States

seen from United States
seen from United States
seen from United States

seen from Türkiye

seen from United States
seen from Singapore

seen from United States

seen from Switzerland

seen from United States

seen from Switzerland
seen from Netherlands
seen from France
@passiveagressiverailsdeveloper
You had a problem with your tests being too damn long. You DRY'd them up by using helpers. Now you have two problems.
state_machine
Well, it has come to this. You wrote this beautiful complex thing of a state_machine. You have 14 states and handle a ton of state changes in various combinations. You also wrote zero docs. Thank you.
You have added to the Gemfile
> You are trying to install in deployment mode after changing your Gemfile. So you haven't updated Gemfile.lock after that reshuffling of gems you did. Consequently, **bundle install --deployment** failed across all servers, prevented servers from restarting, and almost brought the site down. It sure would be very nice if you could run **bundle install** on your side and commit the changes. Which is just what bundler suggests. If you don't want to, it's cool too. Not like it's a big deal or anything.
open(2)
**open()** working with HTTP right away is a lucky coincidence. If you really need that open() to work with HTTP, make sure to require 'open-uri'.