Skip to content

Conversation

@tverney
Copy link
Contributor

@tverney tverney commented Oct 4, 2024

Types of changes

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

Description

Problem

Q dev won't be able to generate code for unrelated prompts. (e.g. explain the code)
It would be a bad CX if Q fail to generate code without guiding users the proper use cases.

Solution

Handle no code change required explicitly.
Allow users to provide more details

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.

@tverney tverney requested review from a team as code owners October 4, 2024 18:20
@tverney tverney requested a review from chengoramazon October 4, 2024 22:58
@tverney tverney requested a review from chengoramazon October 6, 2024 02:46
tverney and others added 2 commits October 9, 2024 15:24
…kits/jetbrains/services/amazonqFeatureDev/controller/FeatureDevController.kt

Co-authored-by: manodnyab <[email protected]>
@tverney tverney requested a review from manodnyab October 9, 2024 19:25
@tverney tverney requested a review from manodnyab October 10, 2024 01:55
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.
…kits/jetbrains/services/amazonqFeatureDev/FeatureDevExceptions.kt

Co-authored-by: Richard Li <[email protected]>
@tverney tverney requested a review from rli October 10, 2024 18:45
@rli rli merged commit a35a059 into aws:main Oct 10, 2024
9 of 12 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.

4 participants