-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: v0.22.5: start fail caused by incorrect migration file naming #3873
Conversation
This issue may only affect those who run memos with postgresql, since I did not found similar naming error in mysql or sqlite migration files. |
And I wondered why it crashed :D Guess I need to wait until it is fixed |
I just tested using |
When will it release, I use the neosmemo/memos:stable docker image and run into this issue yesterday. seems the issue still exist |
Try pull the docker image again. I personally use Re-pulling and recreating the container would fix the issue. |
I had a new pull of the image but had to use |
Thanks, use |
@boojack any news? @RoccoSmit |
@boojack any news? @RoccoSmit |
@mariushosting This patch should have been included in the latest |
Thank you Leo! |
memos failed starting when using PostgreSQL as DB after upgrade to v0.22.5, which the following error message emitted: (docker installation, logs obtained by
docker logs memos
)Which gives error message as below, after unescaping
\t
and\n
:This seems to be caused by the incorrect naming of
store/migration/postgres/prod/0.20/00_reaction.sql
, (only 1 underline between00
andreaction
) which should be00__reaction.sql
. (2 underlines)We could confirm by reading the recent-changed
store/migrator.go
, the constantMigrateFileNameSplit
is defined as__
and this constant is used when splitting the migrate files in functiongetSchemaVersionOfMigrateScript()
.