Amazon Q v1.104.0 EPIPE Failure causing local Knowledge Base to not work
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 807
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 7
Description
## Problem
After upgrading Amazon Q for VSCode to v1.104.0, I am unable to build a local knowledge base for providing Pinned Context.
## Steps to reproduce the issue
- Start VSCode
- Wait
- Get errors
## Expected behavior
To index local knowledge base and allow me to send Pinned Context beyond Active File or Prompts.
## System details (run `AWS: About` and/or `Amazon Q: About`)
- OS: Fedora Linux 42 in WSLv2 on Windows 11.
- Visual Studio Code version: v1.1.06.0
- AWS Toolkit version: v3.84.0
- Amazon Q version: v1.104.0 (also seen now in v1.101.0 and newer)
Contributor guide
Research direction
No source file, test, or entry point is identified. Start by reproducing the failure in VS Code with Amazon Q v1.104.0 or newer on the reported Fedora WSLv2 setup, then inspect the EPIPE error and the local knowledge-base indexing path. Done means the local knowledge base indexes successfully and Pinned Context works beyond the active file or prompts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- ai, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100