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

Hasura Console Fails to Produce Migration Files #9168

Open
eltontian opened this issue Nov 1, 2022 · 1 comment
Open

Hasura Console Fails to Produce Migration Files #9168

eltontian opened this issue Nov 1, 2022 · 1 comment
Labels
k/bug Something isn't working t/native-dbs

Comments

@eltontian
Copy link

Version Information

Server Version:
CLI Version (for CLI related issue): version=v2.14.0-cloud.1

What is the current behaviour?

Sometimes when running sql commands with "This is a migration" checkbox console fails to produce the migration files.

What is the expected behaviour?

Create the the migration files properly.

How to reproduce the issue?

  1. I have seen this a lot immediately after updating the CLI

Any possible solutions/workarounds you're aware of?

When I restart the console it usually resolves itself.
Revert any change, restart the console, and reapply the changes.

However, sometimes you can't revert the changes for example adding enum values so I have to resort to dropping the entire enum and readding it which is cumbersome.

@jonocodes
Copy link

jonocodes commented Jan 18, 2023

Same experience here. Some additional info.

Started hasura using the quickstart using docker.
CLI and engine version 2.16.1

While there are no files being added to my migrations dir I will note that the CLI does seem aware that I am creating them.

➜  hasura git:(main) ✗ hasura migrate status
? Select a database to use All (all available databases)

Database: default
VERSION        NAME  SOURCE STATUS  DATABASE STATUS
1673973119343  init  Present        Present
1674001993633  -     Not Present    Present
1674002011949  -     Not Present    Present
1674002145358  -     Not Present    Present
1674002378091  -     Not Present    Present
1674002543082  -     Not Present    Present
1674002561603  -     Not Present    Present
1674002897509  -     Not Present    Present
1674003453662  -     Not Present    Present

And I can see these migrations in the hdb_catalog.hdb_version table. Perhaps the migrations are being generated but put in another folder or the running container?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k/bug Something isn't working t/native-dbs
Projects
None yet
Development

No branches or pull requests

3 participants