Error when deploying migration
See original GitHub issueI am receiving the following error when trying to run a migration on my database:
LiftEngine:stderr thread 'tokio-runtime-worker-1' panicked at 'old Field for MigrationStep not found', src/libcore/option.rs:1034:5 +0ms
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Error: *** Deployment Failed *** "Migrations" -- invalid sender ...
Issue. Getting this - Error: Deployment Failed "Migrations" -- invalid sender. when trying to deploy to Ropsten Network. Steps to Reproduce
Read more >Error when deploying the Launch Entry configurations in ... - IBM
The following deployment error is thrown whenever there is a Launch Entry (MAXLAUNCHENTRY) associated with one or more signature option flags ( ...
Read more >Common errors and known issues when migration to Azure ...
Overview of common errors when migrating from Cloud Services (classic) to Cloud Service (extended support)
Read more >blockchain - UNABLE TO MIGRATE (Error: Deployment Failed)
It looks like this issue: https://github.com/ethereum/go-ethereum/issues/19424. Because you were sending LES/1 version of transaction ...
Read more >deployment error when migrating from one environment to other
Trying to migrate code using DG and running into issues with source and target shortcut definitions. (1) I created a dynamic deployment group...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Here’s my datamodel, locally I’m using a docker container of postgres, in production I’m using managed postgres from Digital Ocean. Postgres 11 on both.
Here’s a pastebin of the log when I run
DEBUG=* prisma2 lift up
: https://pastebin.com/fUrw2yPgNo problem, was a few versions back.