Is node-resque really compatible with Sidekiq?

Hi, just considering using node-resque combined with sidekiq. I am having some problems with the integration, so I am leaving my feedback here:

• Workers started from node-resque do not show in Sidekiq web. Sidekiq when starting new workers add the name of the worker to the set processes, node-resque doesn’t seem like it does. https://github.com/mperham/sidekiq/blob/4deadba37200bf7812109a2d6de2371727b2ee3f/lib/sidekiq/launcher.rb#L133
• Adding new jobs from node-resque to Sidekiq works fine.
• Stats shown in Sidekiq Web are correctly updated, both failed and processed jobs.
• Scheduled jobs from node-resque are not shown in Sidekiq web (Scheduled tab).
• Scheduled jobs from node-resque requires a worker from node-resque. I add a scheduled job from node-resque using enqueueIn, scheduler is also run in this same process. Sidekiq worker is started and ready to run jobs all the time. After the delay time, nothing happens. To be able to run this job, a worker from node-request must be started.

Please, it would be highly appreciated to document all these caveats (and some others that may exist) in the README for future developers. I don’t think that with current features, and caveats between sidekiq and node-resque should be stated that node-resque is API compatible with Sidekiq because it does not.

Node version: 12.2.0 Ruby version: 2.5.0 Sidekiq Version: 6.0.3. I also checked older versions just in case some fully works. Node-resque version: 6.0.6

[dorthwein]

I’m having trouble enqueing a sidekiq job from node-resque - is it simlpy a matter of calling await queue.enqueue(que, job, args); and setting the correct que and job? Thanks

UPDATE: So by default sidekiq does not have a name space - if you want to schedule from node-resque to sidekiq besure to pass an empty string to your connection namespace. Example below.

 const queue = new Queue(
    {
      connection: {
        pkg: "ioredis",
        host: "127.0.0.1",
        password: null,
        port: 6379,
        database: 0,
        namespace: "",
        // looping: true,
        // options: {password: 'abc'},
      },
    },
    { ...Jobs }
  );

[evantahler]

Thanks for the research @dorthwein! This issue is linked from the Readme, so hopefully this helps others in the future.