Drop-OSS/drop
1
0
Fork 0
mirror of https://github.com/Drop-OSS/drop.git synced 2026-08-26 15:07:58 -04:00
Code Issues 77 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #134] [Bug] Unable to run develop Branch (database error) #71

New Issue
Closed
opened 2026-02-17 17:06:02 -05:00 by yindo · 2 comments
yindo commented 2026-02-17 17:06:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @callephi on GitHub (Jul 13, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/134

In short, previously running nightly, changing the image to develop results in a database error through Drop that prevents the service from being usable.

drop | Error: Could not find Prisma Schema that is required for this command.
drop | You can either provide it with --schema argument,
drop | set it in your prisma.config.ts,
drop | set it as prisma.schema in your package.json,
drop | or put it into the default location (./prisma/schema.prisma, or ./schema.prisma.
drop | Checked following paths:
drop |
drop | schema.prisma: file not found
drop | prisma/schema.prisma: file not found
drop |
drop | See also https://pris.ly/d/prisma-schema-location
drop | enabled metadata provider: GiantBomb
drop | enabled metadata provider: PCGamingWiki
drop | enabled metadata provider: IGDB
drop | Listening on http://[::]:3000
drop-db | 2025-07-14 01:19:05.906 UTC [42] ERROR: column User.profilePicture does not exist at character 283
drop | [unhandledRejection] PrismaClientKnownRequestError:
drop | Invalid prisma.user.upsert() invocation:
drop |
drop |
drop | The column User.profilePicture does not exist in the current database.
drop | at Wn.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:7534)
drop | at Wn.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:6858)
drop | at Wn.request (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:6565)
drop | at async l (/app/app/server/node_modules/@prisma/client/runtime/library.js:130:10067)
drop | at async _Yi0Jzab2kXWILN6Ac3PxEaW7TfnApaoEPGXGQI6VbtE (file:///app/app/server/chunks/nitro/nitro.mjs:1:136705) {
drop | code: 'P2022',
drop | meta: { modelName: 'User', column: 'User.profilePicture' },
drop | clientVersion: '6.5.0'
drop | }
drop | [unhandledRejection] PrismaClientKnownRequestError:
drop | Invalid prisma.applicationSettings.findFirst() invocation:
drop |
drop |
drop | The column ApplicationSettings.enabledAuthencationMechanisms does not exist in the current database.
drop | at Wn.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:7534)
drop | at Wn.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:6858)
drop | at Wn.request (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:6565)
drop | at async l (/app/app/server/node_modules/@prisma/client/runtime/library.js:130:10067)
drop | at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:137927)
drop | at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:137646)
drop | at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:138344)
drop | at async _pnlRnPpbZT7uYrEJrfdoOljTncF1jFl0ZqwKiJfuVwU (file:///app/app/server/chunks/nitro/nitro.mjs:1:158862) {
drop | code: 'P2022',
drop | meta: {
drop | modelName: 'ApplicationSettings',
drop | column: 'ApplicationSettings.enabledAuthencationMechanisms'
drop | },
drop | clientVersion: '6.5.0'
drop | }

Originally created by @callephi on GitHub (Jul 13, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop/issues/134 In short, previously running `nightly`, changing the image to `develop` results in a database error through Drop that prevents the service from being usable. > drop | Error: Could not find Prisma Schema that is required for this command. drop | You can either provide it with `--schema` argument, drop | set it in your `prisma.config.ts`, drop | set it as `prisma.schema` in your package.json, drop | or put it into the default location (`./prisma/schema.prisma`, or `./schema.prisma`. drop | Checked following paths: drop | drop | schema.prisma: file not found drop | prisma/schema.prisma: file not found drop | drop | See also https://pris.ly/d/prisma-schema-location drop | enabled metadata provider: GiantBomb drop | enabled metadata provider: PCGamingWiki drop | enabled metadata provider: IGDB drop | Listening on http://[::]:3000 drop-db | 2025-07-14 01:19:05.906 UTC [42] ERROR: column User.profilePicture does not exist at character 283 drop | [unhandledRejection] PrismaClientKnownRequestError: drop | Invalid `prisma.user.upsert()` invocation: drop | drop | drop | The column `User.profilePicture` does not exist in the current database. drop | at Wn.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:7534) drop | at Wn.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:6858) drop | at Wn.request (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:6565) drop | at async l (/app/app/server/node_modules/@prisma/client/runtime/library.js:130:10067) drop | at async _Yi0Jzab2kXWILN6Ac3PxEaW7TfnApaoEPGXGQI6VbtE (file:///app/app/server/chunks/nitro/nitro.mjs:1:136705) { drop | code: 'P2022', drop | meta: { modelName: 'User', column: 'User.profilePicture' }, drop | clientVersion: '6.5.0' drop | } drop | [unhandledRejection] PrismaClientKnownRequestError: drop | Invalid `prisma.applicationSettings.findFirst()` invocation: drop | drop | drop | The column `ApplicationSettings.enabledAuthencationMechanisms` does not exist in the current database. drop | at Wn.handleRequestError (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:7534) drop | at Wn.handleAndLogRequestError (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:6858) drop | at Wn.request (/app/app/server/node_modules/@prisma/client/runtime/library.js:121:6565) drop | at async l (/app/app/server/node_modules/@prisma/client/runtime/library.js:130:10067) drop | at async Object.pullConfiguration (file:///app/app/server/chunks/nitro/nitro.mjs:1:137927) drop | at async Object.init (file:///app/app/server/chunks/nitro/nitro.mjs:1:137646) drop | at async Object.get (file:///app/app/server/chunks/nitro/nitro.mjs:1:138344) drop | at async _pnlRnPpbZT7uYrEJrfdoOljTncF1jFl0ZqwKiJfuVwU (file:///app/app/server/chunks/nitro/nitro.mjs:1:158862) { drop | code: 'P2022', drop | meta: { drop | modelName: 'ApplicationSettings', drop | column: 'ApplicationSettings.enabledAuthencationMechanisms' drop | }, drop | clientVersion: '6.5.0' drop | }
yindo closed this issue 2026-02-17 17:06:02 -05:00
yindo commented 2026-02-17 17:06:03 -05:00
Author
Owner
Copy Link
Copy Source

@callephi commented on GitHub (Jul 13, 2025):

Was trying to do this as a way to import games without metadata (to circumvent not being able to use metadata for certain games altogether, getting an Error 500 server error), which the nightly branch apparently does not have.

@callephi commented on GitHub (Jul 13, 2025): Was trying to do this as a way to import games without metadata (to circumvent not being able to use metadata for certain games altogether, getting an Error 500 server error), which the nightly branch apparently does not have.
yindo commented 2026-02-17 17:06:03 -05:00
Author
Owner
Copy Link
Copy Source

@DecDuck commented on GitHub (Jul 13, 2025):

The nightly branch should have the ability to import without metadata, have you used docker compose pull?

Edit: also, are you using develop or branch-develop as the tag?

@DecDuck commented on GitHub (Jul 13, 2025): The nightly branch should have the ability to import without metadata, have you used `docker compose pull`? Edit: also, are you using `develop` or `branch-develop` as the tag?
yindo changed title from [Bug] Unable to run develop Branch (database error) to [GH-ISSUE #134] [Bug] Unable to run develop Branch (database error) 2026-06-05 14:21:15 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
duplicate
feature
feature
good first issue
needs-triage
pull-request
Mirrored from GitHub Pull Request
 qol
support
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop#71
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?