-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Handle S3KeySensor in deferrable mode splits bucket_key into individual chars
#52983
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
dominikhei
left a comment
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.
Can you add tests to check list inputs to get_files_async too?
I agree |
|
I'll add those tests - thanks all! |
o-nikolas
left a comment
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.
This issue is so bizarre. I'm curious how we went so long without noticing. Thanks for catching it!
+1 to adding tests
|
@vincbeck, do you mind merging this? |
…dividual chars (apache#52983) * Handle S3KeySensor in deferrable mode splits key into individual chars * Adding tests for passing keys as a list
…dividual chars (apache#52983) * Handle S3KeySensor in deferrable mode splits key into individual chars * Adding tests for passing keys as a list
Per #52920, using the
S3KeySensorin deferrable mode split thebucket_keyparameter into individual characters when passing a string. This PR aims to resolve this by first checking ifbucket_keyis a string, before handling that behavior.Note that two tests were updated as part of this PR. It appears, in fact, that these tests were written to accommodate this faulty logic. This has been fixed.
Closes: #52920