Skip to content

Conversation

@muhammad-othman
Copy link
Member

@muhammad-othman muhammad-othman commented Dec 19, 2025

Description

Modified error response unmarshalling to directly update errorResponse object instead of using intermediate variables. For AWS Query compatible services, error codes are now extracted and set on the errorResponse object within the generate AWSQueryCompatibleBlock, this allowed us to remove conditional AWS Query compatible checks in JsonRPCExceptionUnmarshaller since the errorResponse already contains the proper code and type.

Motivation and Context

DOTNET-8439

Testing

  • Tested some SQS and CloudWatch operations manually and made sure they are throwing the proper exceptions.
  • DRY_RUN-71a1a982-8709-48d3-a99a-c6d4c5251dd8

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • My code follows the code style of this project
  • My change requires a change to the documentation
  • I have updated the documentation accordingly
  • I have read the README document
  • I have added tests to cover my changes
  • All new and existing tests passed

License

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

@peterrsongg peterrsongg self-requested a review December 19, 2025 23:35
Copy link
Contributor

@peterrsongg peterrsongg left a comment

Choose a reason for hiding this comment

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

Verified it works in a console app myself. approved.

"serviceName": "CloudWatch",
"type": "patch",
"changeLogMessages": [
"Improve AWS Query compatible error handling in unmarshallers."
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggestion: Fix error handling for services running in aws query compatible mode, where the generic exception was being thrown instead of specific modeled exceptions

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