-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS Collect: Can't pickle coroutine #423
Comments
Thanks looks like it's a problem from —
And something related to the AWS credentials it's getting. Googling makes it seem related to — aio-libs/aiobotocore#663 But it seems a bit of a rabbit hole that might be better solved by storing credentials however ECS does it? |
Are you running on EKS? Happy to help reproduce if it may be helpful, but probably won't be able to find time until next week. |
Thanks for the quick response! Yes, running on EKS with IRSA. Pulled on that thread a bit more and found:
The solution might be bumping dependencies. Will try to spend some time tomorrow actually looking into this and seeing if a dep version bump might fix. I'll report back if I find anything interesting. |
There's a co-dependency on |
These seem to be working out ok for me:
Should I open against 1.9.6? Are there specific tests you recommend I run? Currently running: |
Hello, hope all is well!
We recently started having some issues with the aws collect connector. I'll start looking into this in more detail tomorrow, but opening this early on the off-chance that someone has already ran into/solved this. Happening on both
1.9.4
and1.9.5
. Prevents SnowAlert from ingesting any aws_collect data.stack trace
The text was updated successfully, but these errors were encountered: