-
Notifications
You must be signed in to change notification settings - Fork 1.1k
PYTHON-5555 Fix AWS Lambda build #2540
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
Did you find the full trackback of the |
Found in your patch:
It seems the task has installed dnspython 2.7.0:
But the AWS Function ends up using a later version of dnspython that has already dropped support for 3.9:
Whereas dnspython 2.7.0 looks like this:
https://github.com/rthalley/dnspython/blob/v2.7.0/dns/exception.py#L51 |
Thanks for tracking that down! |
Updated to use Python 3.10, which solved a dns resolve error on lambda.
I did not find the root cause, but since 3.9 is EOL next month I left it at this solution.
I also updated the errors raised by srv_resolver to include the original error, which was useful in debugging the problem.
Passing build: https://spruce.mongodb.com/task/mongo_python_driver_faas_lambda_test_aws_lambda_deployed_patch_eca38b730b8227c52cd5f0c655f617e969743ee1_68c9e481e31406000770e31e_25_09_16_22_28_25/logs?execution=0