J’ai configuré ce plugin sur mon instance Discourse pour notifier un canal Mattermost lors de nouveaux messages. Cela fonctionne correctement via le bouton de test dans les paramètres du plugin de chat.
J’ai remarqué dans les journaux d’erreur : “Exception de job : constante non initialisée Jobs::NotifyChats. Voulez-vous dire Notification ?”
Backtrace :
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:276:in `const_get'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:276:in `block in constantize'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:273:in `each'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:273:in `inject'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:273:in `constantize'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:132:in `block (5 levels) in dispatch'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/rails.rb:43:in `block in call'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/execution_wrapper.rb:88:in `wrap'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/reloader.rb:72:in `block in wrap'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/execution_wrapper.rb:88:in `wrap'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/reloader.rb:71:in `wrap'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/rails.rb:42:in `call'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:257:in `stats'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/job_logger.rb:13:in `call'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/job_retry.rb:78:in `global'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:124:in `block in dispatch'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/logger.rb:10:in `with'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/job_logger.rb:33:in `prepare'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:123:in `dispatch'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:162:in `process'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:78:in `process_one'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:68:in `run'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/util.rb:15:in `watchdog'
/opt/bitnami/discourse-sidekiq/vendor/bundle/ruby/2.6.0/gems/sidekiq-6.0.7/lib/sidekiq/util.rb:24:in `block in safe_thread'
Si vous avez besoin d’autres informations pour diagnostiquer le problème, n’hésitez pas à demander.