-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fixes 383: Pass parameters to psycopg instead of a connection string #384
Conversation
Ah, maybe not quite:
|
This mostly works, but when I run I'm trying to run the tests on Linux to see if that fixes it.
|
@rustprooflabs: I'm currently running an import and can't run the test due to container name conflicts. This may be ready to go. I'll try to test it later after my import is done, but, I'm pretty swamped.}
I got this on linux which seems very much unrelated. |
@jmealo Thank you for this PR! I'll give this a try in the next couple of days. Assuming nothing major comes up I'd like to get this merged in before next week. |
RE:
I know I've seen this before, you got that when running |
24.04, yep, when running |
Unfortunately, the approach using returncode = helpers.run_command_via_subprocess(cmd=osm2pgsql_command.split(),
cwd=flex_path,
print=True) With the URI style connection string, the
When the
I'm sure this approach could be made to work, but it would take a more significant changes in this project, and likely changes in osm2pgsql-tuner too. In the sake of getting this problem fixed quickly I'm opting for the approach in #386. Thank you for the time you've put into making this project better for everyone! |
This should fix #383.
I didn't have time to get all of the tests passing, but, it's looking like 95%.