Protip: If you don't have a named parameter, don't call it with one. :)
-
-
Replying to @coreyhaines
Haha glad to hear that the error was catching an actual bug!
1 reply 0 retweets 0 likes -
Replying to @sgrif
For sure. I try to live by the mantra "sort isn't broken" when I get an error from tools, especially Rails (5.0.3)
2 replies 0 retweets 0 likes -
Replying to @coreyhaines @sgrif
I do pretty straightforward, simple stuff in Rails, so the chance of it being a PEBKAC issue is VERY HIGH
2 replies 0 retweets 0 likes -
Replying to @coreyhaines
I've seen a lot of places where the solution was "put `serialize :foo` which is what you meant" hence my kneejerk answer
1 reply 0 retweets 0 likes -
-
Replying to @coreyhaines
Yes, and unfortunately it's the kind of case where it feels like a papercut migration pain and not "holy shit this could have been bad"
1 reply 0 retweets 0 likes -
Replying to @sgrif
I do love the idea that I accidentally passed a hash for first parameter, and it got serialized into yaml, then used in the `where` :)
1 reply 0 retweets 0 likes -
Replying to @coreyhaines @sgrif
all I wanted to do was pass the name of the test status. :) Luckily this was just in our test suite, so not a bug in our system.
1 reply 0 retweets 1 like -
Replying to @coreyhaines @sgrif
Upgrading 4.2 to 5, if you can't tell. :)
1 reply 0 retweets 0 likes
Hehe I can tell. :)
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.