Following issue after seemingly successful upgrade on start:
Jun 05 11:20:12 gitea-mirror bun[39685]: 11:20:12 [ERROR] DrizzleError: Failed to run the query '
Jun 05 11:20:12 gitea-mirror bun[39685]: ALTER TABLE `sso_providers` ADD `saml_config` text;'
Jun 05 11:20:12 gitea-mirror bun[39685]: at run (/opt/gitea-mirror/node_modules/drizzle-orm/sqlite-core/session.js:156:17)
Jun 05 11:20:12 gitea-mirror bun[39685]: at migrate (/opt/gitea-mirror/node_modules/drizzle-orm/sqlite-core/dialect.js:662:21)
Jun 05 11:20:12 gitea-mirror bun[39685]: at migrate (/opt/gitea-mirror/node_modules/drizzle-orm/bun-sqlite/migrator.js:4:14)
Jun 05 11:20:12 gitea-mirror bun[39685]: at runDrizzleMigrations (/opt/gitea-mirror/dist/server/chunks/index_DqMeqg5j.mjs:702:7)
Jun 05 11:20:12 gitea-mirror bun[39685]: at /opt/gitea-mirror/dist/server/chunks/index_DqMeqg5j.mjs:726:3
Jun 05 11:20:12 gitea-mirror bun[39685]: at processTicksAndRejections (native:7:39)
Hi @arunavo4
Following issue after seemingly successful upgrade on start:
```bash
Jun 05 11:20:12 gitea-mirror bun[39685]: 11:20:12 [ERROR] DrizzleError: Failed to run the query '
Jun 05 11:20:12 gitea-mirror bun[39685]: ALTER TABLE `sso_providers` ADD `saml_config` text;'
Jun 05 11:20:12 gitea-mirror bun[39685]: at run (/opt/gitea-mirror/node_modules/drizzle-orm/sqlite-core/session.js:156:17)
Jun 05 11:20:12 gitea-mirror bun[39685]: at migrate (/opt/gitea-mirror/node_modules/drizzle-orm/sqlite-core/dialect.js:662:21)
Jun 05 11:20:12 gitea-mirror bun[39685]: at migrate (/opt/gitea-mirror/node_modules/drizzle-orm/bun-sqlite/migrator.js:4:14)
Jun 05 11:20:12 gitea-mirror bun[39685]: at runDrizzleMigrations (/opt/gitea-mirror/dist/server/chunks/index_DqMeqg5j.mjs:702:7)
Jun 05 11:20:12 gitea-mirror bun[39685]: at /opt/gitea-mirror/dist/server/chunks/index_DqMeqg5j.mjs:726:3
Jun 05 11:20:12 gitea-mirror bun[39685]: at processTicksAndRejections (native:7:39)
```
<!-- github-sync-id:4595796387 -->
Shipped in v3.17.1: a pre-migration self-heal step now detects when migration 0013 is pending while saml_config/domain_verified already exist on sso_providers, preserves any SAML config, drops the stranded columns so 0013 can run in full, and restores the data
Glad it's sorted, thanks for confirming! 🎉
Shipped in **[v3.17.1](https://github.com/RayLabsHQ/gitea-mirror/releases/tag/v3.17.1)**: a pre-migration self-heal step now detects when migration `0013` is pending while `saml_config`/`domain_verified` already exist on `sso_providers`, preserves any SAML config, drops the stranded columns so `0013` can run in full, and restores the data
<!-- github-comment-id:4632033734 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi @arunavo4
Following issue after seemingly successful upgrade on start:
Full log:
thx, fixed!
Glad it's sorted, thanks for confirming! 🎉
Shipped in v3.17.1: a pre-migration self-heal step now detects when migration
0013is pending whilesaml_config/domain_verifiedalready exist onsso_providers, preserves any SAML config, drops the stranded columns so0013can run in full, and restores the dataappreciate the quick fix!