The discussion revolves around a bootstrap issue in Discourse where the db:migrate command hangs during the bootstrapping process, specifically when applying a recent migration related to the dismissed_topic_users table neounix. The migration, introduced in commit f5b18e2a, appears to cause the hang with no visible errors in logs neounix. The issue is acknowledged by the Discourse team david, and the problematic migration is quickly reverted in a subsequent commit kris.kotlarek. The user confirms that the issue is resolved in the latest update neounix. The user also notes that the database table from the failed migration remains in place after the revert neounix.
I tend to agree that that this “heavy migration” more-than-likely requires additional review and stringent development testing on a test configuration with a large DB before merged into core. Lucky for our site, I always bootstrap in parallel to production so we did not suffer any downtime during the migration failure(s), so no worries on our end. Thanks for reverting so quickly.
FYI only (just being technically precise, sorry about that… ), I checked the DB after rebuilding just now and the “revert” process did not drop the table from DB, no big deal, just FYI only:
discourse=> \d dismissed_topic_users
Table "public.dismissed_topic_users"
Column | Type | Collation | Nullable | Default
------------+-----------------------------+-----------+----------+---------------------------------------------------
id | bigint | | not null | nextval('dismissed_topic_users_id_seq'::regclass)
user_id | integer | | |
topic_id | integer | | |
created_at | timestamp without time zone | | |
Indexes:
"dismissed_topic_users_pkey" PRIMARY KEY, btree (id)
"index_dismissed_topic_users_on_user_id_and_topic_id" UNIQUE, btree (user_id, topic_id)
Thank you again for your hard work on this and for quickly reverting the migration.