Skip to content
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

Migration fails for stories_order enum #1183

Open
brentcetinich opened this issue Apr 17, 2024 · 1 comment
Open

Migration fails for stories_order enum #1183

brentcetinich opened this issue Apr 17, 2024 · 1 comment

Comments

@brentcetinich
Copy link

I have an old version of stringer and I just built latest image from 40e5a1f. When the container starts the logs are showing the migration is failing with the following error.

I can't tell what version I am coming from as I overwrote the old image :\

Any ideas how to workaround this or how I can see what version I used to have?

stringer  | 2024-04-17 08:40:49,952 INFO success: puma entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
stringer  | 2024-04-17 08:40:51,915 DEBG 'puma' stdout output:
stringer  | rake aborted!
stringer  | StandardError: An error has occurred, this and all later migrations canceled: (StandardError)
stringer  | 
stringer  | Undeclared attribute type for enum 'stories_order'. Enums must be backed by a database column or declared with an explicit type via `attribute`.
stringer  | 
stringer  | 2024-04-17 08:40:51,915 DEBG 'puma' stdout output:
@mockdeep
Copy link
Collaborator

@brentcetinich sorry about that! Is there more log output with a stack trace? It looks to me like it's trying to boot the server before the migration has been run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants