It should fix python-poetry/poetry#2737 as well.

It fixes the root cause, but not the fact that it failed silently.

@ewjoachim yes that is correct. Unfortunately, we need a better way to handle those logs. The issue is that the failure was handled as expected in the sense that current logic explicitly handles the issue by skipping the dependency. Not ideal. Either we need to raise an error gracefully, or simply propagate the relevant log correctly.

It fixes the root cause, but not the fact that it failed silently.

Completely agree that we need to aim for much more robustness.

@PetterS the "failing silently" part was addressed in python-poetry/poetry#2738 & python-poetry/poetry#2739 by @abn and @sdispater ;)