We recently upgraded to 2.4.0.beta5 from 2.4.0.beta4 and sidekiq fails to start with the following traceback: > $ bundle exec sidekiq -C config/sidekiq.yml > uninitialized constant SiteSetting::SiteSettingExtension > /discourse/app/models/site_setting.rb:5:in `<class:SiteSetting>' > /discourse/app/…

I am using the docker commands to test and develop discourse plugins. The other script I am currently using is: # Clear temporary discourse cache and launch development rails vagrant ssh -c '(rm -rf ~/discourse/tmp/cache)' vagrant ssh -c '(cd ~/discourse && sudo bin/docker/rails s)'

[immagine] Falco: Are you running a development install in production :exploding_head:?? Of course not :smile:

@Falco I think it is related to https://github.com/discourse/discourse/commit/427d54b2b00fa94474c0522eaed750452c4e7f43#diff-b2f320bf18d0c321021eb4a8f6704169 What do you think?

Oh it may be. The fact that you didn’t state that this is your development setup and not a dev environment didn’t help. So you are saying that our docker dev setup is currently broken?

[immagine] Falco: So you are saying that our docker dev setup is currently broken? Reverting that commit makes sidekiq work again.

Looks like this is one for you @kris.kotlarek

Ok, I know what happened here, it is my fault. I removed a lot of require_dependency since they are not required anymore when using Zeitwerk autoloader. However, in application.rb we got that: if !Sidekiq.server? config.autoload_paths += Dir["#{config.root}/lib"] end Which means that Sidekiq is…

[immagine] kris.kotlarek: I can bring back that require_depenedency for files which are used by Sidekiq or remove that guard in application.rb . We should remove the guard, I don’t like it cause you have no idea if your process will become a sidekiq or not. In our deployments we have: unicorn…

@kris.kotlarek Thanks for the fix. Sidekiq is now working along with the discourse official plugins :+1: . Most of my 3rd-party plugins with jobs are not working now :cry: . Most likely caused by the following commit not being applied on their Jobs:: classes. :arrow_down: https://github.com/disco…

Sidekiq non si avvia dopo l'attivazione di Zeitwerk in docker dev

Sviluppatore

azawawi (Ahmad M. Zawawi) 4 Ottobre 2019, 5:13am 17

@kris.kotrarek Grazie mille . Ho dato un’occhiata al tuo post sull’autoloader di Zeitwerk. C’è l’intenzione di attivare una funzionalità di auto-ricarica per i plugin in fase di sviluppo per velocizzare lo sviluppo dei plugin?

Argomento		Risposte	Visualizzazioni
Upgrading Discourse to Zeitwerk Development dev-news	13	3405	Ottobre 2, 2019
Sidekiq not working Self-hosting	9	1192	Settembre 2, 2023
"Ensure sidekiq is running." when it is definitely running Self-hosting	18	7880	Ottobre 2, 2015
Development environment : running sidekiq and discourse at startup Development	14	5608	Ottobre 30, 2018
Sidekiq not running. Sidekiq heartbeat test failed, restarting Self-hosting unsupported-install	14	2900	Maggio 11, 2020

Sidekiq non si avvia dopo l'attivazione di Zeitwerk in docker dev

Argomenti correlati