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

telemetry(amazonq): Improving error handling and telemetry in unit test generation #6386

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

ashishrp-aws
Copy link
Contributor

@ashishrp-aws ashishrp-aws commented Jan 16, 2025

Problem

Incorrect handling of errors for 4xx and 5xx on IDE. Proper error messages for users and telemetry needs to differentiate between service errors.

Solution

Copy of @laileni-aws's: telemetry(amazonq): Improving error handling and telemetry in unit test generation. #6187. CLosed 6187 due to rebasing issues and lack of permissions.

  • Adding 4XX vs 5XX httpStatusCode field to amazonq_utgGenerateTests event.
  • Improving error handling in unit test generation.

  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ashishrp-aws ashishrp-aws requested review from a team as code owners January 16, 2025 23:10
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@ashishrp-aws ashishrp-aws changed the title telemetry(amazonq): Improving error handling and telemetry in unit test generation. telemetry(amazonq): Improving error handling and telemetry in unit test generation. Jan 16, 2025
@ashishrp-aws ashishrp-aws changed the title telemetry(amazonq): Improving error handling and telemetry in unit test generation. telemetry(amazonq): Improving error handling and telemetry in unit test generation Jan 17, 2025
Copy link
Contributor

Choose a reason for hiding this comment

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

For reference: as mentioned in #6187 (comment) , this module is not a recommended pattern. Mirroring every single service error manually is a maintenance burden, and doesn't make sense. Either the generated SDK should do this or we should find a programmatic solution.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agreed....we are working on error handling on service side of things. Once those changes are ready. we will make changes here on plugin. But yes, essentially we will get proper errors from the service.

@justinmk3 justinmk3 closed this Jan 17, 2025
auto-merge was automatically disabled January 17, 2025 12:21

Pull request was closed

@justinmk3 justinmk3 reopened this Jan 17, 2025
@justinmk3 justinmk3 merged commit fae084b into aws:master Jan 17, 2025
23 of 24 checks passed
karanA-aws pushed a commit to karanA-aws/aws-toolkit-vscode that referenced this pull request Jan 17, 2025
## Problem
Incorrect handling of errors for 4xx and 5xx on IDE. Proper error
messages for users and telemetry needs to differentiate between service
errors.

## Solution
- Adding 4XX vs 5XX `httpStatusCode` field to `amazonq_utgGenerateTests`
event.
- Improving error handling in unit test generation.
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.

3 participants