-
Notifications
You must be signed in to change notification settings - Fork 20
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
Your request was too big
error on stock RSV repo build via aws-batch
#271
Comments
OSError: [Errno 40] Your request was too big
on stock RSV repo build via aws-batchYour request was too big
error on stock RSV repo build via aws-batch
@corneliusroemer What's the output of |
Hm. This is coming from inside the aiobotocore client used by fsspec/s3fs. My first guess (probably wrong) is that you have an incompatible combination of s3fs and aiobotocore in whatever environment |
|
I ask because I wonder if bioconda/bioconda-recipes#39711 is implicated. Though not certain if the expectation would be that you have a version of |
Ah, the version is 6.2.1, which is after that Conda packaging change. Hmm. |
This is my
Is it ok for boto3 and botocore to have different versions?
|
This seems worth digging into, but I'd love if someone else in @nextstrain/core could pick it up. |
Current Behavior
When trying to run the nextstrain/rsv workflow using
nextstrain build --aws-batch ...
I get an error:botocore.exceptions.ClientError: An error occurred (MaxMessageLengthExceeded) when calling the PutObject operation: Your request was too big.
Expected behavior
It works, I don't get such an error, or at least cli can recover and advise me on how to workaround the issue.
How to reproduce
Steps to reproduce the current behavior:
gh repo clone nextstrain/rsv
Your environment: if running Nextstrain locally
nextstrain.cli 6.2.1
Full logs
The text was updated successfully, but these errors were encountered: