-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
tokio-postgres
v0.7.9 breaks load_config
#1
Comments
ryzhyk
pushed a commit
to feldera/feldera
that referenced
this issue
Aug 24, 2023
Workaround for https: //github.com/3liz/pg-event-server/issues/1, which is caused by https: //github.com/sfackler/rust-postgres/issues/1062 Signed-off-by: Leonid Ryzhyk <[email protected]>
ryzhyk
pushed a commit
to feldera/feldera
that referenced
this issue
Aug 24, 2023
Workaround for https: //github.com/3liz/pg-event-server/issues/1, which is caused by https: //github.com/sfackler/rust-postgres/issues/1062 Signed-off-by: Leonid Ryzhyk <[email protected]>
@ryzhyk Thanks for reporting this ! I updated the dependencies and tests are indeed broken with tokio-postgres v0.7.9. |
They have released v0.7.10 that fix the problem, I will just wait if they are going to yank 0.7.9 before doing anything. |
dmarteau
added a commit
that referenced
this issue
Aug 26, 2023
IMHO a simple warning notice about not using tokio-postgres 1.7.9 should be ok:
|
Tested with 1.7.10 and all is ok. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to this issue,
load_config(None)
now ignores thePGUSER
env variable and setsConfig::user
to the current OS user instead.The text was updated successfully, but these errors were encountered: