Skip to content

[SS-68] iceberg/aws: add more detailed error logging/context#35183

Merged
DAlperin merged 1 commit intoMaterializeInc:mainfrom
DAlperin:dov/iceberg-aws-detailed-error-context
Feb 24, 2026
Merged

[SS-68] iceberg/aws: add more detailed error logging/context#35183
DAlperin merged 1 commit intoMaterializeInc:mainfrom
DAlperin:dov/iceberg-aws-detailed-error-context

Conversation

@DAlperin
Copy link
Member

There is this really weird intermittent failure in prod where it fails to load credentials with http timeout. Cleaning up the context so we know where it might come from is helpful.

@DAlperin DAlperin requested a review from a team February 23, 2026 23:06
@DAlperin DAlperin requested a review from a team as a code owner February 23, 2026 23:06
@github-actions
Copy link

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

  • Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
  • Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
  • Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

  • The PR title is descriptive and will make sense in the git log.
  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).

@DAlperin DAlperin changed the title iceberg/aws: add more detailed error logging/context [SS-68] iceberg/aws: add more detailed error logging/context Feb 24, 2026
Copy link
Contributor

@ublubu ublubu left a comment

Choose a reason for hiding this comment

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

LGTM

One comment inline, looking for a doc comment or name change to clarify how important auth_method()'s output is.

}

impl AwsConnection {
pub(crate) fn auth_method(&self) -> &'static str {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this auth_method string representation somehow canonical? Is it just for display? Is it a key for searching logs?

Copy link
Member Author

Choose a reason for hiding this comment

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

just added to make log searching easy. not super attached to the strings themselves, happy to change

Copy link
Contributor

Choose a reason for hiding this comment

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

I meant that it's not obvious to me, from reading auth_method, what I should feel comfortable using the strings for.

Something like debug_auth_method or a comment on the function.

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point! Fixed

There is this really weird intermittent failure in prod where it fails
to load credentials with http timeout. Cleaning up the context so we
know where it might come from is helpful.
@DAlperin DAlperin force-pushed the dov/iceberg-aws-detailed-error-context branch from 65d6fd5 to dd20aa8 Compare February 24, 2026 22:03
@DAlperin DAlperin enabled auto-merge (squash) February 24, 2026 22:04
@DAlperin DAlperin merged commit aa87532 into MaterializeInc:main Feb 24, 2026
135 checks passed
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