Open peret opened 3 years ago
I have the same issue (cannot upgrade resque-status
past v0.3.0).
Git blame shows that this is the commit that introduced the restriction (resque ~>1.19
) almost 10 years ago.
It also seems like the commit was in response to this issue.
@peret , did you happen to try to build and/or test the latest version of resqueue-status
with the newest version of resque
?
Hello,
I'm investigating an issue we're seeing with exception handling in resque-status. It looks like it's fixed in the latest version of resque-status, however, I can't actually upgrade the gem, because we're using resque 2.0.0. Would you consider opening up the dependency range to allow for later versions of resque as well?
For what it's worth, it looks like we've been unknowingly using resque-status v0.3.0 together with resque 2.0.0 for a while now and we haven't encountered any issues that I know of ;)