Arun Babu Neelicattu

@bryanhughes can you provide the logs of a run where poetry hangs? eg: `poetry update -vvv` Also maybe try using the `--no-ansi` to make sure its not the terminal when...

I don't think this change is required. This makes things less explicit. And relies on implicit behavior. And as mentioned in the referenced PR, that change might not be accepted.

> In the current implementation the directory used is not the current working directory, but ANY directory including or above the current working directory containing a `pyproject.toml`. This is by...

Welp, I missed the question. Just checked the build without the mitigation, and it seems it just "works" now (see https://github.com/abn/reproducer-pip-11368/actions/runs/4957985233/jobs/8870312079). No idea if the root cause somehow got fixed...

@RobinFrcd can you provide a sanitised output of `poetry config repository` please?

@RobinFrcd I am unable to reproduce this. ```console root@610e2455d140:/foobar# poetry add --source private foobar^C root@610e2455d140:/foobar# cat pyproject.toml | tail -n 10 [build-system] requires = ["poetry-core>=1.0.0"] build-backend = "poetry.core.masonry.api" [[tool.poetry.source]] name...

@RobinFrcd yeah; I am aware; i just want to demonstrate that the code got past the credential fetching.

Can you maybe try in a container or a clean environent? Just want to make sure this is not somehting environment specific.

@xmnlab your reported issue not related to the issue discussed here. It looks like you don't have the right keys configured or your network dropped out. @SamuelSmets can you please...

@djeikyb the issue you are facing is not a poetry issue IMHO. This would seem that you didn't have the required system dependencies available for the version of python used...