Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 03 23:05
    beatak commented #26
  • Dec 03 22:31
    beatak commented #240
  • Nov 23 06:14
    zedtux commented #268
  • Nov 22 02:10
    fukayatsu opened #308
  • Nov 01 14:59
    phyzalis commented #111
  • Oct 19 16:54
    iHiD commented #300
  • Oct 19 05:42
    christopheragnus commented #300
  • Oct 16 14:46
    tjozwik commented #234
  • Sep 28 07:53
    256-byte closed #307
  • Sep 21 09:32
    256-byte opened #307
  • Sep 04 23:49
    gilest commented #304
  • Aug 24 20:18
    newtonjose commented #291
  • Aug 11 18:42
    MikeRogers0 commented #297
  • Aug 11 18:30
    honzasterba commented #297
  • Aug 07 21:13
    jerbob92 commented #229
  • Jul 27 19:55
    swiknaba commented #288
  • Jul 27 18:44
    ac21 commented #288
  • Jul 16 05:11
    ftopan80 commented #304
  • Jul 14 01:06
    chienkira commented #304
  • Jul 14 01:06
    chienkira commented #304
gargtushar
@gargtushar
Hey all
anyone here
usui1
@usui1
hello, I have a problem with sidekiq gem after and upgrade from Rails 4.2 to 5.0. For each worker class i get a following error: WARN: NameError: uninitialized constant [CLASSNAME] where CLASSNAME is the name of worker class. I am using Rails ActiveJob and sidekiq-cron to shedule them. It seems that jobs are added but sidekiq can't find the classes to proceed with. Can you help me with this issue?
Antony
@tonymadbrain
hello, have the same problem ^^
Ondřej Bartas
@ondrejbartas
Hi, can you do CLASSNAME.new in rails console? It seems that sidekiq is not starting inside of you rails application
do you start sidekiq from root directory of application? @/all
Abhishek Sarkar
@abhisheksarka
Hi
Does sidekiq-cron schedule jobs using the system cron or is it relying on redis?
nicozhang
@nicozhang
This room is out of date ?
If the task runs error, can i see it from the sidekiq WebUI ?
Alexey Vasiliev
@le0pard
@ondrejbartas hello. Do you still support sidekiq-cron? I want to help in contribution
Ramon Tayag
@ramontayag
The repo is active, but it seems like this room is not
@nicozhang yes, but it will look like a normal sidekiq job that failed
Alexey Vasiliev
@le0pard
@ramontayag do you mean active repo is repo, where last commit was 1 year ago and PRs without review or discussion?
Ramon Tayag
@ramontayag
@le0pard you're right. Takes me a few weeks to realize it's not 2019 anymore