Merge main into feature/dbmod-inputgen #2339
Open
Conversation
This file contains hidden or 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
…ors (#1969) This PR adds comprehensive logging to the Amazon Q Developer Profiles fetching process to help diagnose the "failed to fetch: developerProfiles" error that customers are experiencing with ATX transformation. The enhanced logging captures detailed information about endpoints accessed, regions queried, profiles returned, and provides structured error details without modifying any existing functionality. Key improvements: - Log all endpoints and regions being queried - Capture raw API responses and request parameters - Track profile retrieval success/failure by region - Provide detailed error information including HTTP status codes and AWS metadata - Summarize total profiles fetched across all regions These changes will help identify the root cause of login issues by providing visibility into the profile fetching process. * feat: enhance profile fetching logs to diagnose developerProfiles errors * feat: enhance profile fetching logs and add exception handling for debugging * feat: enhance profile fetching logs and add exception handling for debugging * refactor: remove unused endpoint parameter from fetchProfilesFromRegion
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* feat: mcpmanager changes to support http/sse * fix: fix mcp sse transport headers issue * fix: fix unit tests for mcp http/sse support * feat: ux changes for mcp http/sse support * feat: ux changes for mcp http/sse support
* feat: adding inline chat telemetry * feat: adding error metrics, updating the names of params --------- Co-authored-by: Supraja Venkatesh <[email protected]>
* refactor: separate auto trigger and manual trigger code path * fix: unit test * fix: fix unit test
* fix: use fast glob streaming when collecting files * fix: lower threshold * fix: adjust max files
This change is a test using LFS. It has one small hello world zip (containing a text file that says "hello world"). The purpose of this change is to test some internal processes to ensure they are able to successfully consume the repo once it has LFS contents in it. * chore: define LFS content in a binaries folder as a test * chore: add sample LFS file for a test
This change sets up the repo to: - produce agentic chat builds - maintain alpha/preprod releases - produce release candidate branches This change merges in the feature branch feature/ci-builds. * revert: revert: produce agentic chat bundle from repo (#1827) (#1858) This reverts commit 06b425a. * revert: revert: create GitHub releases for agentic chat alpha, feature, and rc This reverts commit bbd4651. * chore: set agentic version to 1.19.0 * chore: automate creation of release candidate branches (#1842) * fix: ci build packaging (#1879) * chore: produce agentic chat license attribution (#1883) * chore: update qchat binaries, adjust agentic chat version to 1.24.0 (#2016) To prepare this feature branch for a merge to main, this change updates the qserver binaries to the latest version, and sets the agentic chat version manifest to the current version (1.24.0). * chore: update qserver binaries * chore: set agentic version to 1.24.0
- Extend timeout from 10 to 15 minutes (MAX_POLLING_ATTEMPTS: 60 → 90) - Add latency tracking for performance monitoring - Improve error messages for better user experience - Standardize error handling to throw exceptions consistently - Update tests to properly handle exception-based error flow - Add better documentation for timeout constants
## Problem Bring the code we removed previously back https://github.com/aws/language-servers/pull/2424/files#diff-10a12088df160c3eec8bb5eedd826e4ee475614c9b3a544fa2393cdeed92bc24L231-L238 and make the trigger criteria more strict. 1. Non empty right context starting next line 2. Recent edits in the past 20 seconds 3. Classifier result is greater than the threshold ## Solution <!--- REMINDER: - Read CONTRIBUTING.md first. - Add test coverage for your changes. - Link to related issues/commits. - Testing: how did you test your changes? - Screenshots if applicable --> ## License By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
🤖 I have created a release *beep* *boop* --- <details><summary>lsp-codewhisperer: 0.0.88</summary> ## [0.0.88](lsp-codewhisperer/v0.0.87...lsp-codewhisperer/v0.0.88) (2025-10-28) ### Bug Fixes * add venv in the common gitignore patterns ([#2445](#2445)) ([d030288](d030288)) * enforce MAX_TOOL_NAME_LENGTH check in createNamespacedToolName ([#2447](#2447)) ([6663f87](6663f87)) * strenghen NEP trigger conditions ([#2438](#2438)) ([82e2340](82e2340)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please) bot. When you are ready to release these changes, merge this PR. **Blocking GitHub Checks Issue:** if GitHub checks do not run, close and immediately re-open this PR manually.
Co-authored-by: aws-toolkit-automation <>
…g right-click context menu (#2442)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Will Lo <[email protected]>
Co-authored-by: aws-toolkit-automation <>
* chore: add the dummpy package back the the script * chore: fix the zip to cp * chore: move the file into zip folder
#2475) * feat: differenciate implicit and explicit reject for inline completion * fix: add UT for inline reject metric type
Co-authored-by: Boyu <[email protected]>
* fix: McpManager not initialized error * fix: adding more try catch to avoid crashes due to mcpmanager initialization error * fix: adding error to debug logs
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Will Lo <[email protected]>
Co-authored-by: aws-toolkit-automation <>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: aws-toolkit-automation <>
* Revert "fix(amazonq): send full finding details to plugin, partial to agent (#2356)" This reverts commit 961e6ca. * feat(amazonq): if there are more than 30 findings, do not send to agent, only to code issues panel * fix(amazonq): do not stop calling listFindings if there are more than 30 findings * fix(amazonq): do not stop calling listFindings if there are more than 30 findings --------- Co-authored-by: Blake Lazarine <[email protected]>
Error handling in `setPaidTierMode` is broken as it attempts to JSON stringify a circular type which results in the Flare process crashing. This codepath is not new but is now being hit due to a service side change.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Same root cause as #2500
…ead of empty object (#2492) * fix(amazonq): prevent base64 encoding error by passing undefined instead of empty object Fixes #8253, #7896, #8076, #8184 When userInputMessageContext was undefined, it was being replaced with an empty object {}. The AWS SDK's base64 encoder attempted to encode this empty object and threw: "toBase64 encoder function only accepts string | Uint8Array". Changed messageToStreamingMessage() and chatMessageToMessage() to pass undefined instead of {} when userInputMessageContext is not provided. * fix(amazonq): prevent base64 encoding error by passing undefined instead of empty object (#2459) Fixes #8253, #7896, #8076, #8184 When userInputMessageContext was undefined, it was being replaced with an empty object {}. The AWS SDK's base64 encoder attempted to encode this empty object and threw: "toBase64 encoder function only accepts string | Uint8Array". Changed messageToStreamingMessage() and chatMessageToMessage() to pass undefined instead of {} when userInputMessageContext is not provided. --------- Co-authored-by: aws-toolkit-automation <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
36 participants
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):