Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Migrations/seeds doesn't work in Docker and production

See original GitHub issue

Because src/server/migrations isn’t included at all and not ts-node and required directories either. Could be fixed by using a npm run migrate:prod for example. If I find some time in the coming days I’ll put up a PR!

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

sheshbabucommented, Apr 13, 2020

@joenas @mzch This should be fixed in the latest build, sorry for the delay.

0reactions

mzchcommented, Feb 15, 2020

I tried to rebuild freshlytics from sources, and when doing npm run migrate, it reported as below:

error: server "pipelinedb" does not exist
    at Connection.parseE (/srv/freshlytics/freshlytics/node_modules/pg/lib/connection.js:602:11)
    at Connection.parseMessage (/srv/freshlytics/freshlytics/node_modules/pg/lib/connection.js:399:19)
    at Socket.<anonymous> (/srv/freshlytics/freshlytics/node_modules/pg/lib/connection.js:121:22)
    at Socket.emit (events.js:223:5)
    at addChunk (_stream_readable.js:309:12)
    at readableAddChunk (_stream_readable.js:290:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:181:23)

Yes, no foreign server pipelinedb. And if it’s fixed by adding CREATE SERVER "pipelinedb" FOREIGN DATA WRAPPER postgres_fdw; to sql, then CREATE VIEW ... WITH (actioin=materialize) caused error, too.

error: unrecognized parameter "action"
    at Connection.parseE (/srv/freshlytics/freshlytics/node_modules/pg/lib/connection.js:602:11)
    at Connection.parseMessage (/srv/freshlytics/freshlytics/node_modules/pg/lib/connection.js:399:19)
    at Socket.<anonymous> (/srv/freshlytics/freshlytics/node_modules/pg/lib/connection.js:121:22)
    at Socket.emit (events.js:223:5)
    at addChunk (_stream_readable.js:309:12)
    at readableAddChunk (_stream_readable.js:290:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:181:23)

How can this be fixed? Using PostgreSQL 11 and 12 both has the same error.