Chip

@xilefff, do you know if this is still an issue in the GetJobber gem? I see your gem is at 2.0 and theirs is now at 2.1

Yes, my thought was to add some checks on initialization. Try the new endpoints, if they return 404, then fall back to the old. I think this would mean having...

Yes, my though was to add some checks on initialization. Try the new endpoints, if they return 404, then fall back to the old. I think this would mean having...

FWIW, I use rvm and was having this same problem. Using `yard gems --verbose` exposed that the `reek` gem was my problem, too. The error made me think the problem...

I had a stair-stepping memory leak in Heroku running Delayed Job and my app was daily hitting the swap memory line.  I really didn't want...

Ok, so I found the issue: the records were not getting saved because of an `around_create` callback that didn't `yield`. The spec now passes as expected. However, the error message...