Squirrel

I'm facing similar problem which happened on a self-host GitLab PyPI repo too. On version `1.2.2`, `poetry lock` failed, but it works on version `1.1.15`.

As a workaround, I configured `pip` with `.netrc`, which contains the credentials of my private repo. https://pip.pypa.io/en/stable/topics/authentication/#netrc-support

@keriksson-rosenqvist You should store your credentials in `poetry.toml` like @juleswh and remove credentials from `pyproject.toml`. Here is my config that works on version `1.3.2`. ```toml # pyproject.toml [[tool.poetry.source]] name =...

@kristang The second file should be `poetry.toml`, not `poetry.lock`.

@bfontaine I think it is risky that someone places their credentials in `pyproject.toml`. Maybe we just places a warning in document to prohibit this behavior ? CC @sdispater

Same issue here. ```toml [tool.poetry] name = "hello" version = "2020.02.27" description = "zzzz" authors = ["aarrr "] [tool.poetry.dependencies] python = "~2.7 || ~3.7" pytest = "*" firebase-admin = "*"...

Similar issue here. I found woker crashed when backend server of `nchan_(un)subscribe_request` returns non-200 response. Also, with X-Accel feature, workers crashed on 400 response. I guess there may be some...

I'm not sure whether it causes other problem after upgrading some dependencies.