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

fix(storage): nextToken is not surfaced when list result contain only CommonPrefix #13933

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

HuiSF
Copy link
Member

@HuiSF HuiSF commented Oct 17, 2024

Description of changes

It is a legit case that ListObjectV2 returns a result that contains only CommonPrefix[] and without a Content, and NextContinuationToken can be returned as well.

The current implementation omits nextToken for this case, and makes listing next page impossible.

Fix: surface the nextToken

Issue #, if available

Description of how you validated changes

  • manual test with a sample app
  • unit tests

Checklist

  • PR description included
  • yarn test passes
  • Unit Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

Checklist for repo maintainers

  • Verify E2E tests for existing workflows are working as expected or add E2E tests for newly added workflows
  • New source file paths included in this PR have been added to CODEOWNERS, if appropriate

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Copy link
Contributor

@reesscot reesscot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ashika112
Copy link
Member

Thanks Hui Nice Catch !

@HuiSF HuiSF force-pushed the hui/fix/storage/no-next-token branch from 680b1fc to 6de4423 Compare October 17, 2024 18:25
@HuiSF HuiSF merged commit bf58ebc into main Oct 17, 2024
30 checks passed
@HuiSF HuiSF deleted the hui/fix/storage/no-next-token branch October 17, 2024 18:40
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.

5 participants