-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
When not specifying port for Postgres DB port is defaulting to 0 #4756
Labels
Milestone
Comments
alexec
added
the
type/regression
Regression from previous behavior (a specific type of bug)
label
Dec 16, 2020
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Dec 16, 2020
Signed-off-by: Alex Collins <[email protected]>
1 task
Please can you test |
Thanks @alexec for the speedy fix, that LGTM. |
alexec
added a commit
that referenced
this issue
Dec 17, 2020
Signed-off-by: Alex Collins <[email protected]>
simster7
pushed a commit
that referenced
this issue
Jan 4, 2021
Signed-off-by: Alex Collins <[email protected]>
Fix for this is out on https://github.com/argoproj/argo/releases/tag/v2.12.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Summary
It looks like since the changes in #4307 if you do not specify a port for your PG configuration it will now default to
0
since the port type has changed to an integer and the concatenation logic will append:0
to the connection string.Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: