Jacob Chung

refactor(aws-toolkit-vscode): migrate aws-sdk v2 to v3 (#8183) ## Note **There is still a little bit more work needed for fully migrating aws-sdk v2 to v3, specifically all of these clients [here](https://github.com/aws/aws-toolkit-vscode/blob/59fd17fcfa22798e78d0df196290edb4a070f7ec/packages/core/scripts/build/generateServiceClient.ts#L232-L251) from the `generateServiceClient.ts` script** ## Problem AWS SDK V2 is at EOL ## Solution Migrate AWS SDK V2 to V3 This work has been done in the `feature/v2-to-v3-migration` feature branch and thus merging it into `master` Here are the PRs, which this does not include the merges from main and resolving conflicts: - https://github.com/aws/aws-toolkit-vscode/pull/8043 - https://github.com/aws/aws-toolkit-vscode/pull/8042 - https://github.com/aws/aws-toolkit-vscode/pull/8046 - https://github.com/aws/aws-toolkit-vscode/pull/8054 - https://github.com/aws/aws-toolkit-vscode/pull/8041 - https://github.com/aws/aws-toolkit-vscode/pull/8056 - https://github.com/aws/aws-toolkit-vscode/pull/8081 - https://github.com/aws/aws-toolkit-vscode/pull/8069 - https://github.com/aws/aws-toolkit-vscode/pull/8067 - https://github.com/aws/aws-toolkit-vscode/pull/8093 - https://github.com/aws/aws-toolkit-vscode/pull/8095 - https://github.com/aws/aws-toolkit-vscode/pull/8094 - https://github.com/aws/aws-toolkit-vscode/pull/8171 - https://github.com/aws/aws-toolkit-vscode/pull/8159 - https://github.com/aws/aws-toolkit-vscode/pull/8175 - https://github.com/aws/aws-toolkit-vscode/pull/8182 ## Testing Manually tested the [prerelease builds](https://github.com/aws/aws-toolkit-vscode/releases/tag/pre-v2-to-v3-migration) https://github.com/user-attachments/assets/b1d4795c-4027-462e-a195-509ac4a9d8ae --- - 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. --------- Co-authored-by: aws-toolkit-automation <43144436+aws-toolkit-automation@users.noreply.github.com> Co-authored-by: Tai Lai <ctlai95@gmail.com> Co-authored-by: invictus <149003065+ashishrp-aws@users.noreply.github.com> Co-authored-by: Laxman Reddy <141967714+laileni-aws@users.noreply.github.com>

telemetry(amazonq): add feedback functionality with thumbs up/down (#6560) ## Problem - /test and /review are missing thumbs up/down telemetry - /test is missing feedback functionality <img width="545" alt="Screenshot 2025-02-11 at 1 58 42 PM" src="https://github.com/user-attachments/assets/11a46136-46a6-4d35-a7e1-e92f45b1034a" /> <img width="558" alt="Screenshot 2025-02-11 at 1 58 48 PM" src="https://github.com/user-attachments/assets/80288c37-a98c-4e8f-9e32-810238ee2695" /> ## Solution - send telemetry event for thumps up/down for /test and /review - send user feedback for /test which routes to SIM folder - No tests were added as this is UX change --- - 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.

feat(sagemaker): Adding support for Cursor IDE (#8384) (excluding amazonq changes)

feat(amazonq): display test plan summary and refactor shortAnswer to accommodate API changes (#6747) ## Problem - API has been refactored with new fields - shortAnswer will eventually be deprecated - new field jobSummary which has a summary about tests that were generated ## Solution - implemented new field: packageInfoList and its subfields - display test summary in chat https://github.com/user-attachments/assets/23dcdcab-fe08-4f6a-88b6-74940d9ceb57 #### TODO: - integrate new API fields: buildCommand (once build exec is released), packageSummary, fileSummary, etc - remove all unused instances of shortAnswer --- - 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.

build(amazonq): merge release candidate version rc-20251010 (#8169) ## Problem This merges the released changes for rc-20251010 into main. MCM-136118981 ## Solution --- - 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. --------- Co-authored-by: aws-toolkit-automation <>

test(amazonq): E2E tests for /test #6431 ## Problem - There are currently no E2E tests for /test ## Solution - Created E2E tests for /test: view diff, accept, reject, unsupported language, external file

test(amazonq): reset state after each testgen e2e test (#6522) ## Problem 1. The /test command can occasionally create test files in directories unrelated to the source file location (this is a known science issue that will be addressed) 2. Unit tests generated after the "Clicks on accept" test may possibly accumulate in the CI since testFixtures isn't reset for each build. This can lead to bloated test environments as these tests should be isolated and start with a clean state. ## Solution 1. Add a dedicated testgen folder within testFixtures to isolate from other files. This prevents cross-contamination (ex: python tests appearing in java directories) 2. Clean up generated unit tests after "Clicks on accept" test --- - 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.

feat(amazonq): bundle stripped indexing folder for @file support in fallback LSP (#8591) ## Problem When users behind corporate proxies/firewalls can't download the LSP from CDN, the extension falls back to a bundled LSP. The bundled LSP currently excludes the entire indexing/ folder (~200MB), which means @file, @folder, and @code context commands don't work for these users. ## Solution Instead of deleting the entire `indexing` folder during bundling, selectively strip only the heavy platform-specific files that aren't needed for context commands: - dist/bin/ — ONNX native binaries (25MB) - dist/build/ — faiss native binaries (11MB) - models/ — CodeSage ONNX model (124MB) This keeps extension.js, lspServer.js, tree-sitter WASMs (~30MB uncompressed, ~3MB compressed in VSIX), which is everything needed for @file, @folder, @code, and BM25 cross-file context. VSIX size impact: +3MB (19MB → 22MB) Depends on https://github.com/aws/language-servers/pull/2629: (CDN must have the updated indexing library)

fix(amazonq): revert update LSP client info name for sagemaker unified studio #7786 (#7813) Reverts aws/aws-toolkit-vscode#7786 This revert PR will fix the failing tests here: https://d1ihu6zq92vp9p.cloudfront.net/c6d9931c-1deb-46ae-ae59-a3d205835a39/report.html Linux Unit Tests are passing 4252/4252: https://d1ihu6zq92vp9p.cloudfront.net/e705989e-fe51-45e4-9772-7ed2ef7eb3fb/report.html

fix(toolkit): add missing sagemakerSshKiro extension ID and getIdeInfo from skipped Cursor IDE commit