Skip to content
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

revert accidental dupe of _register_s3_events #867

Merged
merged 1 commit into from
Nov 26, 2021

Conversation

eoghanmurray
Copy link
Contributor

@eoghanmurray eoghanmurray commented Jun 3, 2021

This looks to have been accidentally inserted in 3faf885 — on the basis that the line is identical to the next one.

This actually causes failures for me down in the bowels of botocore, as it tries to rewrite to 'virtual' urls or something and I get a failure s3-accelerate.amazonaws.com cannot be found.... this is because my bucket subdomain has been stripped out (there's no DNS entry for s3-accelerate.amazonaws.com which becomes the target after the second _register_s3_events call; the bucket is stripped from the URL)

FYI In a previous debug session when I thought the problem was in botocore, I traced the problem to some operations that were introduced in boto/botocore@28b8831

This looks to have been accidentally inserted in aio-libs@3faf885 — on the basis that the line is identical to the next one.

This actually causes failures for me down in the bowels of botocore, as it tries to rewrite to 'virtual' urls or something and I get a failure `s3-accelerate.amazonaws.com` cannot be found.... this is because my bucket subdomain has been stripped out (there's no DNS entry for `s3-accelerate.amazonaws.com` which becomes the target after the second `_register_s3_events` call; the bucket is stripped from the URL)

FYI In a previous debug session when I thought the problem was in botocore, I traced the problem to some operations that were introduced in boto/botocore@28b8831
@thehesiod
Copy link
Collaborator

ooo thanks, wonder how that happened. Would be nice if we port a test to check for this

@eoghanmurray
Copy link
Contributor Author

I noticed a comment in botocore along the lines of 'this is safe to change the subdomain as we've already ' ... something related to virtual endpoints/urls which I didn't understand.
Maybe we could raise an issue in botocore to say that _register_s3_events isn't idempotent.
I'm a very much arms length user of all this (including s3) so I won't be able to contribute any further debugging time :(

@thehesiod thehesiod merged commit 018e2dd into aio-libs:master Nov 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants