Oops after updating to discouse 2.9 due to Discourse QA plugin

Product Support

AI-generated summary

After updating to Discourse 2.9, user yhmtsai encountered an “Oops” error upon login, with a NoMethodError in the production log related to the QA plugin. The issue persisted even after restarting the server. yhmtsai resolved it by removing the QA plugin from app.yml. sam clarified that the Discourse Q&A plugin is under review by the team and should not be used until an official announcement, and the error is likely no longer an issue.

1

after update to discourse 2.9, when I login to discourse website, it gives Oops page.
If no login, all are fine.

image
after restarting, it only takes 1s but it is still failed.

I got the following from rails/production.log

Started GET "/" for 46.223.162.135 at 2022-02-08 21:56:20 +0000
Processing by ListController#latest as HTML
Completed 500 Internal Server Error in 40ms (ActiveRecord: 0.0ms | Allocations: 12759)
NoMethodError (undefined method `>=' for nil:NilClass)
(eval):72:in `_fast_attributes'
app/controllers/application_controller.rb:605:in `preload_current_user_data'
app/controllers/application_controller.rb:411:in `preload_json'
app/controllers/application_controller.rb:387:in `block in with_resolved_locale'
app/controllers/application_controller.rb:387:in `with_resolved_locale'
lib/middleware/omniauth_bypass_middleware.rb:71:in `call'
lib/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:356:in `call'
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/enforce_hostname.rb:23:in `call'
lib/middleware/request_tracker.rb:198:in `call'

safe-mode also happen.

Is there anything I can try or provide?

2

after I delete the QA plugin from app.yml, it works again.

3

The Discourse Q&A plugin is in the process of being adopted by the Discourse team.

I recommend against installing it anywhere until @tgxworld makes the announcement that we are ready.

That said, it is very likely the error reported here is no longer an issue.