Panic while connecting to invalid address

[jbergstroem]

Panic while connecting to invalid address

[tolgaOzen]

Hello @jbergstroem, this issue will be resolved in version 0.7.5. We have added it to the roadmap

[tolgaOzen]

Hi @jbergstroem , we resolved this issue in version v0.7.5. Could you try it and close the issue if it's resolved?

[jbergstroem]

Right now it seems to exit with the help flag; not sure how useful that is to have in your logs? Perhaps just exit cleanly with "retries exceeded, exiting"

[jbergstroem]

Also, the string formatting for the message seems broken (using same docker command as above):

time=2024-02-24T18:27:47.935Z level=ERROR msg="failed to migrate database: %w" !BADKEY="failed to connect to `host=localhost user=user database=db`: dial error (dial tcp [::1]:5432: connect: cannot assign requested address)"
time=2024-02-24T18:28:29.797Z level=ERROR msg="failed to initialize database: %w" !BADKEY="failed to connect to `host=localhost user=user database=db`: dial error (dial tcp [::1]:5432: connect: cannot assign requested address)"

[tolgaOzen]

Hello @jbergstroem, we've made an update regarding this. Can you try it in v0.7.7?

[jbergstroem]

The error stings are now fixed but I still think its strange to exit with a help message? The user is not invoking the command incorrectly, rather passing incorrect options. I would prefer a final error message in style with "Could not connect to database after N retries. Exiting."

[tolgaOzen]

Can you open a different issue for this? @jbergstroem

[jbergstroem]

Closing since it no longer panics.

Move the side thread about exit behavior to #1092