Dependency error when building Cloud Function about pubsub2inbox

[rosmo]

Thanks, I've seen that before but weirdly it doesn't happen on the container build. What Python version are you using, the default?

[coachtinho]

On the Cloud Function, "python38". However, now that you mentioned it, I noticed that requirements.txt was generated using Python 3.9, and when I ran pip-compile myself, I used Python 3.10. Maybe it's related to that.

[rosmo]

It wasn't a Python issue, but some additional dependencies needed to be pinned and --allow-unsafe flag to be passed. I've fixed it now and also improved the Terraform code a bit.

[coachtinho]

It's working fine now. Thank you!

Closing this issue.

[coachtinho]

I'm running into this issue again. I tried updating the branch with your most recent changes but it didn't work. Also tried running the pip-compile command again. The error message is the exact same as before, but it displays a different link for the googleapis-common-protos package:

googleapis-common-protos<2.0dev,>=1.56.2 from https://files.pythonhosted.org/packages/76/b9/fc6a31a90e3c78cea00d209d48f1e5c6c9edc6b14f3039470c3f7fae60a1/googleapis_common_protos-1.57.1-py2.py3-none-any.whl (from google-api-core[grpc]==2.10.2->-r requirements.txt (line 194)); Error ID: 0ea8a540

[rosmo]

Yeah, it's pretty strange. It seems to work fine when the pipeline builds the container or whenever I do it locally. I have googleapis-common-protos also both in requirements.txt.in and the generated requirements.txt. What Python runtime version are you using?

[coachtinho]

On my machine, I'm running Python 3.10. The Cloud Function is using "python38".

[rosmo]

Well, that was a bit of an issue. I think the root cause is because pip-compile generates a dependency to googleapis-common-protos[grpc] no matter how much you try to force it use the one without the grpc qualifier. I fixed it by manually editing the requirements.txt to remove the [grpc] part. I think it's a pip bug but you can't fix it inside the Cloud Function environment.

I've pushed the fix and tagged a new release 1.4.7.

(just leaving the comment here in case someone stumbled upon this by search)

[rosmo]

@coachtinho Did you get this to work?

[coachtinho]

Sorry for the late response, I've been away for a while. Just tested it and seems to be working properly.

Thank you for the updates, closing the issue.