-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
RecursionError: Maximum recursion depth exceeded #4061
Comments
I am facing this maximum recursion depth issue suddenly as well when trying to check if the object exists in the s3 bucket using
It used to work before but not sure if something changed suddenly.
|
Hi @MustaphaU, thanks for reaching out. If you limit the script to only be initializing a client (no actual operations), do you still have this behavior? In other words, what is the minimum reproducible code snippet that produces this recursion depth error? Thanks! |
Hi @RyanFitzSimmonsAK
Thank you. Edit: The error persists. Apologies for the back and forth. Yes, |
I am also getting the same error. It was working fine a few weeks ago. |
So, s3.Bucket(settings.S3_BUCKET).put_object(Key=key, Body=file_data) works, but the following code doesn't. This is a nightmare :) res = self.s3.put_object(Bucket=settings.S3_BUCKET,
Key=key,
Body=file_data) |
Probably same thing goes to get_object |
Describe the bug
I need help with this recursion error
maximum recursion depth exceeded
from boto3. This occurs when I initialize an s3 client in my inference script to allow me read s3 objects. Your insights will be deeply appreciated! Similar issue was posted on stackoverflow 2 months ago here: https://stackoverflow.com/questions/77786275/aws-sagemaker-endpoint-maximum-recursion-depth-exceeded-error-when-calling-botoHere is the relevant code block responsible for the error:
Expected Behavior
The s3 client created to enable access to the s3 objects
Current Behavior
Here is the full error log:
Reproduction Steps
simply initializing an s3 client within an inference script like so:
Possible Solution
No response
Additional Information/Context
No response
SDK version used
1.34.55
Environment details (OS name and version, etc.)
Sagemaker endpoint for Tensorflow serving
The text was updated successfully, but these errors were encountered: