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

Migrations not working in 1.0.1 with go1.13 #1563

Closed
Munsio opened this issue Sep 17, 2019 · 1 comment · Fixed by #1565
Closed

Migrations not working in 1.0.1 with go1.13 #1563

Munsio opened this issue Sep 17, 2019 · 1 comment · Fixed by #1565
Assignees
Labels
bug Something is not working.
Milestone

Comments

@Munsio
Copy link

Munsio commented Sep 17, 2019

I updated from hydra 1.0.0 to 1.0.1 with a fresh development install but the "migrate sql" command failed to create all needed database schemas - does anyone encounter the same problem?

Using docker-compose starting up a mysql 5.7 instance und using docker environment var for DSN key

the problem occurs during parse operation of the DSN

error output:

time="2019-09-17T08:36:49Z" level=info msg="Establishing connection with SQL database backend" dsn="root:secret@tcp(mysqld:3306)/mysql?parseTime=true://*:*@tcp(mysqld:3306)/mysql?parseTime=true"
time="2019-09-17T08:36:49Z" level=info msg="Successfully connected to SQL database backend" dsn="root:secret@tcp(mysqld:3306)/mysql?parseTime=true://*:*@tcp(mysqld:3306)/mysql?parseTime=true"
Got dsn: mysql://root:secret@tcp(mysqld:3306)/mysql?max_conns=20&max_idle_conns=4Usage:
  hydra migrate sql <database-url> [flags]

Flags:
  -h, --help            help for sql
  -e, --read-from-env   If set, reads the database connection string from the environment variable DSN or config file key dsn.
  -y, --yes             If set all confirmation requests are accepted without user interaction.

Global Flags:
      --config string     Config file (default is $HOME/.hydra.yaml)
      --skip-tls-verify   Foolishly accept TLS certificates signed by unkown certificate authorities


parse mysql://root:secret@tcp(mysqld:3306)/mysql?max_conns=20&max_idle_conns=4: invalid port ":3306)" after host
@Munsio
Copy link
Author

Munsio commented Sep 17, 2019

@aeneasr stated that this is a known bug and a fix should comming soon

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

Successfully merging a pull request may close this issue.

2 participants