Running into an error while building for 1.12.0 and 1.12.1:
pangolin[427113]: Stack: SqliteError: no such table: hostMeta
pangolin[427113]: at Database.prepare (..pangolin-1.12.1/share/pangolin/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
pangolin[427113]: at BetterSQLiteSession.prepareQuery ..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/better-sqlite3/session.js:23:30)
pangolin[427113]: at BetterSQLiteSession.prepareOneTimeQuery ..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/sqlite-core/session.js:141:17)
pangolin[427113]: at SQLiteSelectBase._prepare (..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:615:88)
pangolin[427113]: at SQLiteSelectBase.all (..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:641:17)
pangolin[427113]: at SQLiteSelectBase.execute (..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:650:17)
pangolin[427113]: at SQLiteSelectBase.then(..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/query-promise.js:21:17) {"error":{"code":"SQLITE_ERROR"}}
This seems like the migrations are not being run successfully. The next build and all other build steps are run correctly AFAIK. I have set $BUILD to "oss". I hope i am missing a build step or something. Any pointers?
Originally created by @jackrosenberg on GitHub (Nov 3, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1804
### Describe the Bug
Hey team,
Running into an error while building for 1.12.0 and 1.12.1:
```
pangolin[427113]: Stack: SqliteError: no such table: hostMeta
pangolin[427113]: at Database.prepare (..pangolin-1.12.1/share/pangolin/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
pangolin[427113]: at BetterSQLiteSession.prepareQuery ..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/better-sqlite3/session.js:23:30)
pangolin[427113]: at BetterSQLiteSession.prepareOneTimeQuery ..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/sqlite-core/session.js:141:17)
pangolin[427113]: at SQLiteSelectBase._prepare (..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:615:88)
pangolin[427113]: at SQLiteSelectBase.all (..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:641:17)
pangolin[427113]: at SQLiteSelectBase.execute (..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/sqlite-core/query-builders/select.js:650:17)
pangolin[427113]: at SQLiteSelectBase.then(..pangolin-1.12.1/share/pangolin/node_modules/drizzle-orm/query-promise.js:21:17) {"error":{"code":"SQLITE_ERROR"}}
```
This seems like the migrations are not being run successfully. The next build and all other build steps are run correctly AFAIK. I have set `$BUILD` to `"oss"`. I hope i am missing a build step or something. Any pointers?
### Environment
- OS Type & Version: NixOS (master: 0be01004)
- Pangolin Version: 1.12.0/1
- Gerbil Version: na
- Traefik Version: na
- Newt Version: na
- Olm Version: na
### To Reproduce
Kinda complicated if not running NixOs, this is the code i have changed since last working version :
https://github.com/NixOS/nixpkgs/pull/458076
### Expected Behavior
Migrations should run successfully.
@github-actions[bot] commented on GitHub (Nov 18, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3544490163 -->
@github-actions[bot] commented on GitHub (Nov 18, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@oschwartz10612 commented on GitHub (Nov 22, 2025):
Hey sorry it took me a while to get to this. Did you end up figuring it out?
What do the wider logs look like? Does it get to trying to run
migrations after the initial database build already occurs? That could
be causing the issue is it thinks its migrating but the database has not
been built yet with the latest sql from drizzle.
<!-- gh-comment-id:3566898002 -->
@oschwartz10612 commented on GitHub (Nov 22, 2025):
Hey sorry it took me a while to get to this. Did you end up figuring it out?
What do the wider logs look like? Does it get to trying to run
migrations after the initial database build already occurs? That could
be causing the issue is it thinks its migrating but the database has not
been built yet with the latest sql from drizzle.
@github-actions[bot] commented on GitHub (Dec 8, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3623922121 -->
@github-actions[bot] commented on GitHub (Dec 8, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@jackrosenberg commented on GitHub (Dec 13, 2025):
Sorry, took me a while to get back to this too. Found it, i wasn't running the migrations 🤡
<!-- gh-comment-id:3649511283 -->
@jackrosenberg commented on GitHub (Dec 13, 2025):
Sorry, took me a while to get back to this too. Found it, i wasn't running the migrations 🤡
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.
Originally created by @jackrosenberg on GitHub (Nov 3, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1804
Describe the Bug
Hey team,
Running into an error while building for 1.12.0 and 1.12.1:
This seems like the migrations are not being run successfully. The next build and all other build steps are run correctly AFAIK. I have set
$BUILDto"oss". I hope i am missing a build step or something. Any pointers?Environment
To Reproduce
Kinda complicated if not running NixOs, this is the code i have changed since last working version :
https://github.com/NixOS/nixpkgs/pull/458076
Expected Behavior
Migrations should run successfully.
@github-actions[bot] commented on GitHub (Nov 18, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@oschwartz10612 commented on GitHub (Nov 22, 2025):
Hey sorry it took me a while to get to this. Did you end up figuring it out?
What do the wider logs look like? Does it get to trying to run
migrations after the initial database build already occurs? That could
be causing the issue is it thinks its migrating but the database has not
been built yet with the latest sql from drizzle.
@github-actions[bot] commented on GitHub (Dec 8, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@jackrosenberg commented on GitHub (Dec 13, 2025):
Sorry, took me a while to get back to this too. Found it, i wasn't running the migrations 🤡