I have been using this library for over a year now without any issues at all.
Now when I try to deploy a google cloud function (python37) with slackclient==2.7.0 or slackclient==2.7.3 or even slackclient==2.0.0, the function cannot be deployed anymore.
The error from google cloud build is:
ERROR: (gcloud.functions.deploy) OperationError: code=13, message=Function deployment failed due to a health check failure. This usually indicates that your code was built successfully but failed during a test execution. Examine the logs to determine the cause. Try deploying again in a few minutes if it appears to be transient.
As soon as I remove the slack client from my cloud function, it deploys without any problems. The last successful deployment with the slack client was on 14th July 2020. I am having this problem with all of my cloud functions that use the slack client.
Anyone know what can be the issue here ? Why does the slack client all of a sudden fail the "Health Check" ?
@minniss I haven't tried this out on my own yet but allow me to ask a few questions for more details.
Now when I try to deploy a google cloud function (python37) with slackclient==2.7.0 or slackclient==2.7.3 or even slackclient==2.0.0, the function cannot be deployed anymore.
The title of this issue mentions v2.7.0 specifically but it seems your issue is not slackclient's version-specific. This situation arises with any versions of slackclient, right?
Is it possible to ask you to provide more information about the repro steps? I can deploy a cloud function on my own but if you have any specific steps that may affect, knowing those may be helpful to figure out the cause.
Hi @seratch,
Supporting @minniss's comment, I'm having the same issue with slackclient==2.5.0 (I tried with 2.7.0 too). No specific steps, just importing slack client's library.
Thank you!



Thanks. I just confirmed anyone can easily reproduce this situation with slackclient package while it doesn't happen with other PyPI packages (I've verified with boto3).
It seems to be an issue on Google Cloud side. It fails with Python 3.7 while it works with Python 3.8 (beta) 馃

The current workaround is to specify yarl==1.4.2 in your requirements.txt
Thanks, I worked for me!
yarl is one of aiohttp's dependencies. Its latest version 1.5.0 was released two days ago.
Probably, the version is incompatible with the Google Cloud Functions runtime.
Thanks @takura !! This also works for me.. I owe you a beer next time you are in Belgium 馃槃
As we found a workaround for it, please allow me to close this issue. Thanks a lot for flagging this @minniss and we really appreciate your help @takura !
I know this is closed issue but does anyone have issuetracker in google?
We are also affected by this
Here you go: https://issuetracker.google.com/issues/162329927
ohh it's P1! the fix should be fast 馃檹
Most helpful comment
The current workaround is to specify yarl==1.4.2 in your requirements.txt