UPDATE: @NateDhaliwal rightfully points out my accessing the DB in after_initializer may break the rules - I was just lucky for a long time. I’m going to make some changes. I’m getting: ActiveRecord::NoDatabaseError: We could not find your database: discourse_test. Available database configuratio…

Not 100% sure, but I think it happens if you use ActiveRecord through things like User, etc openly, e.g. not in on() or in a job but just in after_initialize. I encountered this too not long ago… IIRC I had to ask AI for this; I moved the code to a scheduled job and it was fine after that.

Apologies, on second look it does seem to be failing on my code, but I am accessing it in after_initialize Looks like the rules might have changed: user_count = User.count doesn’t look legal in an initializer anymore (perhaps it was always bad practice) thanks for the suggestion! :clap: I think…

No problem, glad you got it working!

Unerwarteter Fehler in CI

Entwickler

NateDhaliwal (Nate Dhaliwal) 13. August 2025 um 00:07 5

Kein Problem, ich freue mich, dass es funktioniert hat!

Thema		Antworten	Aufrufe
Database "discourse_development" does not exist Development	3	2170	8. Oktober 2019
Error while trying to remove the Anti-Spam Akismet plugin Self-hosting akismet	2	491	31. März 2023
Discourse AI Install Failing Self-hosting ai	19	288	18. Juli 2024
[ E 2023-02-09 19:25:44.6204 217094/T1o age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /home/feedback/discour Self-hosting unsupported-install	4	1018	11. Februar 2023
"Error log: raising while migrating the discourse table Self-hosting	0	636	7. März 2022

Unerwarteter Fehler in CI

Verwandte Themen