cannot open file diff from amazon Q with title "Original ↔ Current"

[HKLongSon]

Problem

Steps to reproduce the issue

1. reuqest Amazon Q edit any file
2. click file in tab Amazone Q changed
3. in vs studio open tab error with content bug: The editor could not be opened due to an unexpected error. Please consult the log for more details.

Expected behavior

open file diff with code changed by Amazone Q

System details (run AWS: About and/or Amazon Q: About)

• OS:
• Visual Studio Code version: 1.104.0
• Amazon Q version: 1.94.0

[geogeno]

I had the same problem. In rolling Amazon Q back to 1.93.0, the problem cleared up completely. I am running VSCode 1.104.1, on Windows 11 Pro Build 26100.ge_release.240331-1435. My main Windows system runs on NTFS and my development drive is exFAT.

Under 1.94.0, when Q made a change and I attempted to see the diff by clicking on the chat bubble. My experience was that when Amazon Q's chat says that it has altered a file it shows something like "INDEX.md +60 -11". Clicking on this chat bubble should open a view of the file with the changes in a split file screen with changes showing. The dialog that presents now is "Unable to open '\PRM\dev\wam-pi\INDEX.md (Original <-> Current, Editable)' and a note that says "Unable to resolve resource g:%5CPRM%5Cdev%5Cwam-pi%5CINDEX.md" (NOTE: my dev space is on a local g: drive. However, moving the project to the NTFS c: drive did not change the problem.)

My resolution included deleting all workspace content for VSCode from %APPDATA%\Code\User\workspaceStorage. While that did not solve the problem it did clear the workspaceStorage. At that point I rolled the extension back to 1.93.0, opened the project afresh and diff bubbles now present as they should with old vs new placed side by side. The project now works as it did before the update and from the exFAT drive.

AWS, check your extension.

[ashishrp-aws]

fix for the issue: #8047. Releasing this Thursday in next update. Please use version 1.93.0 for now to mitigate. Version 1.95.0 should have the fix

[HKLongSon]

Hi @geogeno, @ashishrp-aws
I solved this issue by updating the extension to version 1.93.0.
Thank you so much for your help!