You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ x] I have searched the issues of this repo and believe that this is not a duplicate.
[x ] I have consulted the FAQ and blog for any relevant entries or release notes.
[x ] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.
Issue
I've been using google-cloud-pipeline-components with the above versions of poetry and python without issues for months. Since last night I've been unable to add that dependency to existing poetry-based projects or ones with empty toml files. The poetry add step runs for hours; I eventually kill the process.
I piped the output to a file and ran cat against it while the add operation was running. I saw references to conflicts between google-api-core and other dependencies. Based on what I found in the log I tried pinning google-api-core to version 1.34.0 and added it first. Then I added google-cloud-pipeline-components. Both adds ran in fractions of a second.
Later I tried a poetry install with a lock file built from the two-step process above. It hung. I tried clearing my poetry cache and rerunning. It's been running for hours.
I'm running an add that normally works and trying on multiple machines, operating systems, and networks. Pinning versions seems to be the workaround. I don't have resolution or even an acceptable workaround but I'm still debugging.
Thank you.
The text was updated successfully, but these errors were encountered:
I tried downgrading this specific project to python 3.10 and all dependencies were pulled quickly, without error, and without pinning. I'm going to keep it on 3.10 for now.
google-cloud-pipeline-components works in one of my python 3.11 projects so I'm confused.
-vvv
option) and have included the output below.Issue
I've been using
google-cloud-pipeline-components
with the above versions of poetry and python without issues for months. Since last night I've been unable to add that dependency to existing poetry-based projects or ones with empty toml files. The poetry add step runs for hours; I eventually kill the process.I piped the output to a file and ran cat against it while the add operation was running. I saw references to conflicts between
google-api-core
and other dependencies. Based on what I found in the log I tried pinninggoogle-api-core
to version 1.34.0 and added it first. Then I addedgoogle-cloud-pipeline-components
. Both adds ran in fractions of a second.Later I tried a poetry install with a lock file built from the two-step process above. It hung. I tried clearing my poetry cache and rerunning. It's been running for hours.
I'm running an add that normally works and trying on multiple machines, operating systems, and networks. Pinning versions seems to be the workaround. I don't have resolution or even an acceptable workaround but I'm still debugging.
Thank you.
The text was updated successfully, but these errors were encountered: