Alex Sharp

@renchap Is it on the roadmap to fix this? Currently this repo is incompatible with the latest stable release of rails (5.2). Is this repo still active?

Apologies it took me so long to get to this. Completely missed the notification on this.

I'm having this same issue. Is there any support for swapping out the xml parsing backend for something like nokogiri?

Which part did you rewrite? Is it open source?

@bsl not to my knowledge, unfortunately. I think what we need at this point is an actively maintained fork of the xmpp4r library.

Here's the backtrace: ``` → VVERBOSE=1 QUEUE=* bundle exec ./bin/rake environment resque:work ** [02:52:25 2013-04-17] 30473: Starting worker 12-345-67-890:1234:* ** [02:52:25 2013-04-17] 30473: Registered signals ** [02:52:25 2013-04-17] 30473: Pruning...

Just updating this ticket -- it's worth mentioning that this was a job coming from resque-scheduler. I'm not sure if the code path is different there, but I'm trying to...

@codebycliff or someone who has commit on this repo -- can you either mark this repo as inactive, find a new maintainer, or redirect people to an active fork? Thank...

I get this as well. Either an error in the code or in the README.

Looking at the relevant part of the code, there is a bug where the `data['actions']` part of the params hash is built: ``` ruby def create(description, priority, filter, actions) data...