Skip to content

chore: Merge from main. #1383

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

Merged
merged 77 commits into from
May 20, 2025
Merged

chore: Merge from main. #1383

merged 77 commits into from
May 20, 2025

Conversation

laileni-aws
Copy link
Contributor

Problem

Solution

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

jguoamz and others added 30 commits May 6, 2025 16:31
* fix: errors/cancellation not resetting undoAll state

* test: add unit tests

* test: update test

* style: revert formatting change
…ws#1278)

* fix: improve data synchronization of server side workspace context

* fix: adding catch to snapshotWorkspace call

---------

Co-authored-by: Weitao Wang <[email protected]>
Co-authored-by: Paras <[email protected]>
* fix: use the correct command name for testing bundles

* chore: change return type to pipe to see if more logs can be available

---------

Co-authored-by: Paras <[email protected]>
…n be 0 (aws#1272)

* fix: regex should match workspace text in bold style and startLine can be 0

* fix: remove unintended debug lines
Problem
Currently when the chat loads up a UI ready event is sent to the lsp, to load up previous chats and start indexing. If loading of previous chats fail, the LSP process crashes. This is particularly evident when openTab event has not been handled by the client.
An error in that flow should not crash the LSP process or block the rest of the indexing from continuing.

Solution
This change surrounds the load chat logic within a try catch of its own to allow the rest of the indexing logic to proceed and not crash the server process
* fix: undo buttom not dimmed the card

* fix: fix more regression case for reject
* fix: permission ux

* fix: minor edits
…eivedLatency (aws#1285)

## Problem
events between vscode and flare are not aligned

## Solution
add codewhispererCustomizationArn
…s#1259)

* fix: add tooltip for warning message

* fix: fix the string

* fix: add enum

* fix: remove numbers

* fix: the icon for different category icon and reject button
…rectory ends with a slash (aws#1302)

* fix: add visibleName property to fix empty directory name when the directory ends with a slash

* fix: format

---------

Co-authored-by: Francesco Piccoli <[email protected]>
* chore(release): release packages from branch main

* fix: update versions manually (release-please bug)

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Francesco Piccoli <[email protected]>
…meter (aws#1300)

* fix: for exportResultsArchive to call with profileArn
---------

Co-authored-by: Pranav Firake <[email protected]>
github-actions bot and others added 25 commits May 14, 2025 15:31
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Problem:
Forcing commit-lint locally is very disruptive.

Solution:
Drop it.
…etrics (aws#1341)

* fix: adding new telemetry metrics and addtional fields for existing metrics

* Minor edits

* fix: failing tests

* fix: adding agenticCodingMode to emitMessageResponseError metric
* feat: migrate inline completion telemetry to Flare

* feat: migrate inline completion telemetry to Flare
Bumps the typescript-eslint group with 2 updates: [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) and [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser).


Updates `@typescript-eslint/eslint-plugin` from 8.31.0 to 8.31.1
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.31.1/packages/eslint-plugin)

Updates `@typescript-eslint/parser` from 8.31.0 to 8.31.1
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.31.1/packages/parser)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/eslint-plugin"
  dependency-version: 8.31.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: typescript-eslint
- dependency-name: "@typescript-eslint/parser"
  dependency-version: 8.31.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: typescript-eslint
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Current export chat functionality doesn't properly handle user cancellation of the save dialog, leading to incorrect telemetry reporting and runs into errors.

Solution
Added proper handling of save dialog cancellation.
Enhanced error handling to differentiate between user cancellation and other failure cases.
Updated telemetry emission to accurately reflect the export operation outcome.
…x tests (aws#1353)

This change address a few different things concerning the usage of `workspaceFolders` across servers.
* Language server runtime version has been bumped to the latest to pull changes made in aws/language-server-runtimes#509
* All locations that determine workspaceFolders have been updated to call `workspace.getAllWorkspaceFolders()` which was introduced in the runtimes PR as a common utility(it respects `didChangeWorkspaceFolder` event alongwith using rootUri of initializeparams in absence of `workspaceFolder`)
* With this update, particularly in the VS client paths associated with tool actions are now correct. Prior to that they were displayed as a relativePath.
* InitializeUtils has been deleted as the logic has been moved to the runtimes repo

In addition, this change fixes test failures seen locally on Windows devices associated with  `workspaceUtils.test.ts` and `fileSearch.test.ts` whereever `fs.readDir` calls were being stubbed out. Error `path is undefined` was being thrown for tests where `getEntryPath` was invoked.
* Revert "fix: convert RTS improperly formed request error to 500 (aws#1356)"

This reverts commit 9d74a17.

* Revert "fix: re-categorize error status code (aws#1355)"

This reverts commit a98a842.
…ws#1372)

* fix: Truncate API request first, then truncate chat history
* feat: initial modifications for launching one container per workspace

* feat: use real workspaceIdentifier passed from extensions

* chore: add singleton consumer of message queue

* fix: prevent hang from remoteWorkspaceIdPromise under race condition

* fix: eliminate dependency upload issues

* feat: make artifacts upload obey global size limit

* fix: prevent existing .classpath being overridden

* chore: add back client-side a/b testing check

* chore: fix TypeScript ESLint rule violations

* chore: refactor WebSocketClient send method

---------

Co-authored-by: Jiatong Li <[email protected]>
Co-authored-by: Weitao Wang <[email protected]>
* fix: stop buttom work expected

* fix: stop text align with agentic reply

* fix: when user input a prompt, it wont have stop message before the new prompt

* fix: remove the unused center stop message and add comment
…ws#1373)

* fix: missing handle connection expired error

* fix: translate to responseError

* fix: update translate logic
@laileni-aws laileni-aws requested a review from a team as a code owner May 20, 2025 05:14
@laileni-aws
Copy link
Contributor Author

Trying to keep parity between main and agentic-chat branches

@laileni-aws laileni-aws merged commit 020d453 into aws:agentic-mcp May 20, 2025
@laileni-aws laileni-aws deleted the parity branch May 28, 2025 17:26
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.