-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Unable to parse response (no element found: line 1, column 0), invalid XML received. Further retries may succeed #392
Comments
This looks like a bug in |
they will not fix it, it's integration issue |
They seem to be pointing towards This is the code snippet that seems to be failing for you.
Can you run this and see if you get the same error? |
|
Where did you run that code? Seems like you already have some event loop going, are you using Ipython? |
Yes, inside notebook This is result from Ipython
|
Ok then you don't need to start the loop in the notebook. from aiobotocore.session import get_session
session = get_session()
async with session.create_client("iam") as iam:
async for page in iam.get_paginator("list_roles").paginate():
for role in page["Roles"]:
print(await iam.list_role_tags(RoleName=role["RoleName"])) |
Same with #392 (comment) |
Ok but if you use |
|
Can you set |
Works!
|
Hi @jacobtomlinson, But if I skip the clean_up, I have to manually delete the cluster. |
No you don't. When you create a cluster it tries to clean up any old broken clusters that may exist, this is what you are skipping. |
I'm getting the same error on an EC2 cluster. Any idea how to workaround that? The skip_cleanup argument isn't present for the EC2Cluster object. |
In case it's helpful, it only happens when I increase the cluster size from 100 to 1000 machines |
It sounds like AWS is giving some API response to botocore that it can't parse when making a large number of API requests. @secrettoad could you share the traceback so we can see which API calls in |
I will get this error sometimes before I start the cluster, but after a few times of retry, it finally succussed.
The text was updated successfully, but these errors were encountered: