Skip to content

Conversation

@chengoramazon
Copy link
Contributor

@chengoramazon chengoramazon commented Oct 8, 2024

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Description

Problem

  • Upload url would expire in a given time. The original error message is not clear for users what to do next.

Solution

  • Handle URL expiry explicitly.
  • Add a clear error message.
JBExpired

Checklist

  • My code follows the code style of this project
  • I have added tests to cover my changes
  • A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
  • I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

@chengoramazon chengoramazon marked this pull request as ready for review October 9, 2024 14:20
@chengoramazon chengoramazon requested review from a team as code owners October 9, 2024 14:20
@chengoramazon chengoramazon merged commit 7e4f6e3 into aws:main Oct 9, 2024
9 of 12 checks passed
rli pushed a commit that referenced this pull request Oct 10, 2024
…servability (#4953)

**Problem:** Feature dev instrumentation 1) records all failures as `FeatureDevException`, losing information about the specific exception type, and 2) lacks annotation of `reasonDesc` and the operation related to the error. (By operation, although we do capture `amazonq_codeGenerationInvoke`,  we're missing the subprocess name such as `StartCodeGeneration`.) As a result, we do not have insight into feature dev failures in JetBrains.


**Solution:** 1) Update exception modeling pattern for feature dev functionality to derive subclasses of `FeatureDevException`, providing a meaningful class name when inspected as error `reason`. 2) On `FeatureDevException`, accept an `operation` and `desc` to provide further annotation (merged when logged as `reasonDesc`).

This change will have conflicts with #4938 and #4949. I'll rebase on top of those and reconcile any drift in a subsequent revision.
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