github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-15 21:31:24 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #3018] 1.18.3 - Appears to cause Sqlite Mirgration Issues #27914

New Issue
Closed
opened 2026-06-10 23:30:07 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-06-10 23:30:07 -05:00
Owner
Copy Link

Originally created by @JDKB22 on GitHub (May 7, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/3018

Originally assigned to: @oschwartz10612 on GitHub.

Describe the Bug

After updating to EE-1.18.3 from 1.18.3 it appears this creates an issue for the migration process for an sqlite DB.

2026-05-07T01:07:35.368059728Z Starting migrations from version 1.18.2
2026-05-07T01:07:35.369929162Z Migrations to run: 1.18.3
2026-05-07T01:07:35.370123576Z Running migration 1.18.3
2026-05-07T01:07:35.373945495Z Running setup script 1.18.3...
2026-05-07T01:07:35.377334455Z Failed to migrate db: SqliteError: table 'trialNotifications' already exists
2026-05-07T01:07:35.377356096Z at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
2026-05-07T01:07:35.377359319Z at file:///app/dist/migrations.mjs:5370:11
2026-05-07T01:07:35.377382479Z at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24)
2026-05-07T01:07:35.377385484Z at Object.migration34 [as run] (file:///app/dist/migrations.mjs:5381:7)
2026-05-07T01:07:35.377388041Z at executeScripts (file:///app/dist/migrations.mjs:5594:27)
2026-05-07T01:07:35.377390552Z at async runMigrations (file:///app/dist/migrations.mjs:5551:7)
2026-05-07T01:07:35.377393151Z at async run (file:///app/dist/migrations.mjs:5524:3)
2026-05-07T01:07:35.377395555Z at async file:///app/dist/migrations.mjs:5522:1 {
2026-05-07T01:07:35.377398111Z code: 'SQLITE_ERROR'
2026-05-07T01:07:35.377400496Z }
2026-05-07T01:07:35.377797645Z Failed to run migration 1.18.3: SqliteError: table 'trialNotifications' already exists
2026-05-07T01:07:35.377810977Z at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
2026-05-07T01:07:35.377813777Z at file:///app/dist/migrations.mjs:5370:11
2026-05-07T01:07:35.377817211Z at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24)
2026-05-07T01:07:35.377819824Z at Object.migration34 [as run] (file:///app/dist/migrations.mjs:5381:7)
2026-05-07T01:07:35.377822454Z at executeScripts (file:///app/dist/migrations.mjs:5594:27)
2026-05-07T01:07:35.377825191Z at async runMigrations (file:///app/dist/migrations.mjs:5551:7)
2026-05-07T01:07:35.377827713Z at async run (file:///app/dist/migrations.mjs:5524:3)
2026-05-07T01:07:35.377830308Z at async file:///app/dist/migrations.mjs:5522:1 {
2026-05-07T01:07:35.377832755Z code: 'SQLITE_ERROR'
2026-05-07T01:07:35.377835157Z }
2026-05-07T01:07:35.378005693Z Migration process failed: SqliteError: table 'trialNotifications' already exists
2026-05-07T01:07:35.378012410Z at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
2026-05-07T01:07:35.378015234Z at file:///app/dist/migrations.mjs:5370:11
2026-05-07T01:07:35.378032310Z at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24)
2026-05-07T01:07:35.378035228Z at Object.migration34 [as run] (file:///app/dist/migrations.mjs:5381:7)
2026-05-07T01:07:35.378037737Z at executeScripts (file:///app/dist/migrations.mjs:5594:27)
2026-05-07T01:07:35.378040403Z at async runMigrations (file:///app/dist/migrations.mjs:5551:7)
2026-05-07T01:07:35.378043041Z at async run (file:///app/dist/migrations.mjs:5524:3)
2026-05-07T01:07:35.378045584Z at async file:///app/dist/migrations.mjs:5522:1 {
2026-05-07T01:07:35.378048069Z code: 'SQLITE_ERROR'
2026-05-07T01:07:35.378050690Z }
2026-05-07T01:07:35.378250243Z Error running migrations: SqliteError: table 'trialNotifications' already exists
2026-05-07T01:07:35.378257020Z at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
2026-05-07T01:07:35.378259717Z at file:///app/dist/migrations.mjs:5370:11
2026-05-07T01:07:35.378262162Z at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24)
2026-05-07T01:07:35.378264848Z at Object.migration34 [as run] (file:///app/dist/migrations.mjs:5381:7)
2026-05-07T01:07:35.378267509Z at executeScripts (file:///app/dist/migrations.mjs:5594:27)
2026-05-07T01:07:35.378270014Z at async runMigrations (file:///app/dist/migrations.mjs:5551:7)
2026-05-07T01:07:35.378272608Z at async run (file:///app/dist/migrations.mjs:5524:3)
2026-05-07T01:07:35.378275159Z at async file:///app/dist/migrations.mjs:5522:1 {
2026-05-07T01:07:35.378277628Z code: 'SQLITE_ERROR'
2026-05-07T01:07:35.378280103Z }

Environment

  • OS Type & Version: Ubuntu 24.04.4 LTS
  • Pangolin Version: pangolin:ee-1.18.3
  • Gerbil Version: gerbil:1.3.1
  • Traefik Version: V3.6
  • Newt Version: 1.12.3
  • Olm Version: (if applicable)

To Reproduce

Update from 1.18.2 to 1.18.3

Expected Behavior

This should follow the normal upgrade process and not hang on the Sqlite Migration.

Originally created by @JDKB22 on GitHub (May 7, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/3018 Originally assigned to: @oschwartz10612 on GitHub. ### Describe the Bug After updating to EE-1.18.3 from 1.18.3 it appears this creates an issue for the migration process for an sqlite DB. > 2026-05-07T01:07:35.368059728Z Starting migrations from version 1.18.2 2026-05-07T01:07:35.369929162Z Migrations to run: 1.18.3 2026-05-07T01:07:35.370123576Z Running migration 1.18.3 2026-05-07T01:07:35.373945495Z Running setup script 1.18.3... 2026-05-07T01:07:35.377334455Z Failed to migrate db: SqliteError: table 'trialNotifications' already exists 2026-05-07T01:07:35.377356096Z at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21) 2026-05-07T01:07:35.377359319Z at file:///app/dist/migrations.mjs:5370:11 2026-05-07T01:07:35.377382479Z at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24) 2026-05-07T01:07:35.377385484Z at Object.migration34 [as run] (file:///app/dist/migrations.mjs:5381:7) 2026-05-07T01:07:35.377388041Z at executeScripts (file:///app/dist/migrations.mjs:5594:27) 2026-05-07T01:07:35.377390552Z at async runMigrations (file:///app/dist/migrations.mjs:5551:7) 2026-05-07T01:07:35.377393151Z at async run (file:///app/dist/migrations.mjs:5524:3) 2026-05-07T01:07:35.377395555Z at async file:///app/dist/migrations.mjs:5522:1 { 2026-05-07T01:07:35.377398111Z code: 'SQLITE_ERROR' 2026-05-07T01:07:35.377400496Z } 2026-05-07T01:07:35.377797645Z Failed to run migration 1.18.3: SqliteError: table 'trialNotifications' already exists 2026-05-07T01:07:35.377810977Z at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21) 2026-05-07T01:07:35.377813777Z at file:///app/dist/migrations.mjs:5370:11 2026-05-07T01:07:35.377817211Z at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24) 2026-05-07T01:07:35.377819824Z at Object.migration34 [as run] (file:///app/dist/migrations.mjs:5381:7) 2026-05-07T01:07:35.377822454Z at executeScripts (file:///app/dist/migrations.mjs:5594:27) 2026-05-07T01:07:35.377825191Z at async runMigrations (file:///app/dist/migrations.mjs:5551:7) 2026-05-07T01:07:35.377827713Z at async run (file:///app/dist/migrations.mjs:5524:3) 2026-05-07T01:07:35.377830308Z at async file:///app/dist/migrations.mjs:5522:1 { 2026-05-07T01:07:35.377832755Z code: 'SQLITE_ERROR' 2026-05-07T01:07:35.377835157Z } 2026-05-07T01:07:35.378005693Z Migration process failed: SqliteError: table 'trialNotifications' already exists 2026-05-07T01:07:35.378012410Z at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21) 2026-05-07T01:07:35.378015234Z at file:///app/dist/migrations.mjs:5370:11 2026-05-07T01:07:35.378032310Z at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24) 2026-05-07T01:07:35.378035228Z at Object.migration34 [as run] (file:///app/dist/migrations.mjs:5381:7) 2026-05-07T01:07:35.378037737Z at executeScripts (file:///app/dist/migrations.mjs:5594:27) 2026-05-07T01:07:35.378040403Z at async runMigrations (file:///app/dist/migrations.mjs:5551:7) 2026-05-07T01:07:35.378043041Z at async run (file:///app/dist/migrations.mjs:5524:3) 2026-05-07T01:07:35.378045584Z at async file:///app/dist/migrations.mjs:5522:1 { 2026-05-07T01:07:35.378048069Z code: 'SQLITE_ERROR' 2026-05-07T01:07:35.378050690Z } 2026-05-07T01:07:35.378250243Z Error running migrations: SqliteError: table 'trialNotifications' already exists 2026-05-07T01:07:35.378257020Z at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21) 2026-05-07T01:07:35.378259717Z at file:///app/dist/migrations.mjs:5370:11 2026-05-07T01:07:35.378262162Z at sqliteTransaction (/app/node_modules/better-sqlite3/lib/methods/transaction.js:65:24) 2026-05-07T01:07:35.378264848Z at Object.migration34 [as run] (file:///app/dist/migrations.mjs:5381:7) 2026-05-07T01:07:35.378267509Z at executeScripts (file:///app/dist/migrations.mjs:5594:27) 2026-05-07T01:07:35.378270014Z at async runMigrations (file:///app/dist/migrations.mjs:5551:7) 2026-05-07T01:07:35.378272608Z at async run (file:///app/dist/migrations.mjs:5524:3) 2026-05-07T01:07:35.378275159Z at async file:///app/dist/migrations.mjs:5522:1 { 2026-05-07T01:07:35.378277628Z code: 'SQLITE_ERROR' 2026-05-07T01:07:35.378280103Z } ### Environment - OS Type & Version: Ubuntu 24.04.4 LTS - Pangolin Version: pangolin:ee-1.18.3 - Gerbil Version: gerbil:1.3.1 - Traefik Version: V3.6 - Newt Version: 1.12.3 - Olm Version: (if applicable) ### To Reproduce Update from 1.18.2 to 1.18.3 ### Expected Behavior This should follow the normal upgrade process and not hang on the Sqlite Migration.
GiteaMirror commented 2026-06-10 23:30:08 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (May 7, 2026):

Looking into it

<!-- gh-comment-id:4393623275 --> @oschwartz10612 commented on GitHub (May 7, 2026): Looking into it
GiteaMirror commented 2026-06-10 23:30:09 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (May 7, 2026):

Fixed by #3021 pushing over the tag now

<!-- gh-comment-id:4393868423 --> @oschwartz10612 commented on GitHub (May 7, 2026): Fixed by #3021 pushing over the tag now
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#27914
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?