Matt Conway

I originally ported this from https://github.com/wr0ngway/resque-dynamic-queues and used https://github.com/wr0ngway/resque-queue-priority to dynamically handle priorities, so it made sense to sort the queues because that was the base resque behavior. I didn't...

Ok, added you as a collaborator. When doing a release, I typically, check in a new version.rb with a bumped version number (semantic versioning), then check in an updated changelog...

Depending on how logstash parses it, you may be able to do so right now via log4r's MDC by setting the prefix to and empty string ( https://github.com/wr0ngway/log4r-gelf/blob/master/lib/log4r-gelf/gelf_outputter.rb#L90 ) ```...

Although, now that I look at the logstash doc you linked to, I think that tags fields in the logstash config is globally applied to all events received from gelf....

Yes, sorry, I haven't touched resque in a long time. Happy to hand over maintenance to contributors if you'd like to be able to push gems, etc.

Yup, sorry, I was only doing a prototype with sidekiq which never went anywhere. Feel free to fork it - or if you want, I can make you a contributor.

I think this is because of how jest isolates context, as described here: https://backend.cafe/should-you-use-jest-as-a-testing-library I also see it when doing a simple Array instancesof: ``` expect(result.data).toBeInstanceOf(Array); // Expected constructor: Array...