Skip to content

Remove usage of DisplayName API from S3 integ test as S3 no longer sends it #6305

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

Merged
merged 3 commits into from
Jul 30, 2025

Conversation

joviegas
Copy link
Contributor

@joviegas joviegas commented Jul 29, 2025

Motivation and Context

Java.lang.NullPointerException
    at software.amazon.awssdk.services.s3.S3ListObjectsV2IntegrationTest.assertS3ObjectSummariesAreValid(S3ListObjectsV2IntegrationTest.java:335)
    at software.amazon.awssdk.services.s3.S3ListObjectsV2IntegrationTest.testListWithFetchOwner(S3ListObjectsV2IntegrationTest.java:262)
    at java.lang.reflect.Method.invoke(Method.java:498)

https://docs.aws.amazon.com/AmazonS3/latest/API/API_Owner.html

  • based on this
Between July 15, 2025 and October 1, 2025, you will begin to see an increasing rate of missing DisplayName in the Owner object.

Modifications

  • Remove the usage of DisplayName API in iteg test , we already do check on the owner.id api

License

  • I confirm that this pull request can be released under the Apache 2 license

@joviegas joviegas requested a review from a team as a code owner July 29, 2025 22:43
@joviegas joviegas changed the title Joviegas/ddb eventual consistency Remove usage of DisplayName API from S3 integ test as S3 no longer sends it Jul 29, 2025
Copy link

@joviegas joviegas added this pull request to the merge queue Jul 29, 2025
Merged via the queue into master with commit f75ba18 Jul 30, 2025
36 of 38 checks passed
Copy link

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants