Skip to content

Conversation

@alxndrsn
Copy link
Contributor

@alxndrsn alxndrsn commented Nov 2, 2025

Closes getodk/central#1469

What has been done to verify that this works as intended?

Updated tests.

Why is this the best possible solution? Were any other approaches considered?

Alternative discussed at getodk/central#1469 - the approach in this PR is the simple+quick+low-risk approach.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

No effect.

Does this change require updates to the API documentation? If so, please update docs/api.yaml as part of this PR.

No.

Before submitting this PR, please make sure you have:

  • run make test and confirmed all checks still pass OR confirm CircleCI build passes
  • verified that any code from external sources are properly credited in comments or that everything is internally sourced

@alxndrsn alxndrsn marked this pull request as ready for review November 2, 2025 11:15
@alxndrsn alxndrsn changed the title s3: improve upstream internal error messages s3: improve upstream internal error logging Nov 5, 2025
@alxndrsn alxndrsn merged commit 7adcba3 into getodk:master Nov 12, 2025
6 checks passed
@alxndrsn alxndrsn deleted the improve-amazon-internal-error-reporting branch November 12, 2025 05:49
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.

[backend] upstream s3 error messages don't contain useful information

2 participants