Merge master into feature/agentic-chat #6914
Merged
+1,830
−1,369
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Problem Users lose all chats when they close VSCode, and there's no way to browse through chat history. Users also cant export their conversations to an easily shareable format. ## Solution Automatically persist conversations to JSON files in `~/.aws/amazonq/history`, one for each workspace where Amazon Q chats occur. Add chat history and chat export buttons to top of Amazon Q toolbar. Clicking on the chat history button allows users to browse and search through chat history. Users click on an old conversation to open it back up (currently open conversations are in bold). Clicking on chat export button allows users to save chat transcript as a markdown or html. Note: persistence + history is only for Q Chat Tabs (not /dev, /doc, /transform, etc.)
|
feat(amazonq): automatically generate fix without clicking Generate Fix button
…ateMachine in CDK Applications (#6874) ## Problem As we added support for WorkflowStudio in Toolkit for editing ASL language files, we want to upgrade the render StateMachine Graph in CDK applications experience with the a readonly mode of WorkflowStudio which has better visualization, a code pane for view ASL definition, an export mechanism for exporting ASL definition in JSON/YAML or PNG/SVG. ## Solution Removed the old visualization classes that links to the legacy renderer CDN. From the `renderStateMachineGraphCDK` wizard, upon finding the `template.json` file for a specific stateMachine, we send the file uri to WorkflowStudioEditorProvider to open a readonly WFS to render the StateMachine Graph. --- - 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](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license.
## Problem Users currently cannot access logs generated by the Agent when it executes user commands during code generation. ## Solution The output generated by the Agent during user command execution will be captured and written to the user's `logs`. This ensures that: - Command execution logs are persisted locally - Users can access the logs directly from their repository for troubleshooting.
## Problem unreliable test fix #6913 ## Solution Move the spy instantiation closer to reduce side effects. Add delay before start running command so additional for clean up to reduce chance of flakiness. Change assertion from true/false to count comparison to give more info for debugging in case the flakiness persists into the future.
## Problem clicking the Export button on a fresh conversation doesn't include answers from Q in the exported markdown/html. Answers are included if Export is clicked after closing/reopening IDE ## Solution hide export chat from tab bar
## Problem /review test is flaky, but I was not able to reproduce. ## Solution skip this test for this week to unblock
## Problem fix #6921 ## Solution Refactor the tests for cleaner creating and deletion template.yaml file. - Scope and group tests cases based on required starting template. - Update assertion and error message.
## Problem Need to add additional fields to the chat history schema to support agentic chat ## Solution - Create new Message type to store all history fields - Add messageToChatMessage converter - Replace use of ChatItem type with Message type - Use messageToChatMessage converter to create triggerPayload history
Problem:
SSH Agent
can start the agent on windows:
Error: Test length exceeded max duration: 30 seconds
[No Pending UI Elements Found]
at Timeout._onTimeout (D:\a\aws-toolkit-vscode\aws-toolkit-vscode\packages\core\src\test\setupUtil.ts:46:32)
Solution:
- retry 2 times.
Problem:
Unhandled promise rejection results in mysterious CI log message:
rejected promise not handled within 1 second:
Error: Command exited with non-zero code: 1
Solution:
Include the command name+args in the rejection message.
tsmithsz
approved these changes
Apr 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automatic merge failed
Command line hint
To perform the merge from the command line, you could do something like the following (where "origin" is the name of the remote in your local git repo):
Testing