Frequently unable to use Copilot Chat in Visual Studio 2022 Preview - 'There was a problem completing your request. Please try again'

[chrisrlewis]

Select Topic Area

Bug

Body

I have seen this discussion in other threads, and each one seems to be closed without resolution or explanation.

I am seeing this more frequently since updating to Version 17.13.0 Preview 2.1.

Yesterday, when it occurred again I closed down all instances of VS, restarted and all was well. This morning, the problem is back again.

Here is the output, with local paths redacted:

[Conversations Information] [SemanticContextService] Generating semantic context for C:\xxxxxxxxxxxxxxxxxxxxxxxxxxx.
[Conversations Information] [SemanticContextService] ContextBuilder instance created. Initial fetched types from document count: 7, Initial fetched context from document count: 10.
[Conversations Information] [SemanticContextService] Generating context with reference hops...
[Conversations Information] [SemanticContextService] Processing reference hop 1...
[Conversations Error] [SemanticContextService] An error occurred while extracting code for file: C:\xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[Conversations Error] [SemanticContextService] An error occurred while extracting code for file: C:\xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[Conversations Information] [SemanticContextService] Context with reference hops generated. Total types: 11, Total context: 11.
[Conversations Information] [SemanticContextService] Calculating Jaccard Similarity for definition context and taking top 100 from max of 1000 files
[Conversations Error] [SemanticContextService] Error encountered while generating semantic context: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\xxxxxxxxxxxxxxxxxxxxxxxxxxxx'.
at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode) at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode)
at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode) at System.IO.FileStream..ctor(String path, FileStreamOptions options) at System.IO.File.Open(String path, FileStreamOptions options) at Microsoft.VisualStudio.Copilot.CodeIndex.FileOperationHelper.GetSharedStreamReader(String filePath) in D:\a\_work\1\s\src\Copilot.CodeIndex\FileOperationHelper.cs:line 26 at Microsoft.VisualStudio.Copilot.CodeIndex.FileOperationHelper.ReadAllTextSharedAsync(String filePath, CancellationToken cancellationToken) in D:\a\_work\1\s\src\Copilot.CodeIndex\FileOperationHelper.cs:line 20 at Microsoft.VisualStudio.Copilot.CodeIndex.Infrastructure.Context.ContextRankingManager.OrderByJaccardSimilarityAsync(IReadOnlyList1 definitionContext, String userQuery, CancellationToken cancellationToken, String selectedCodeString) in D:\a_work\1\s\src\Copilot.CodeIndex\Infrastructure\Context\ContextRankingManager.cs:line 107
at Microsoft.VisualStudio.Copilot.CodeIndex.Infrastructure.Context.ContextRankingManager.GetOrderedContextAsync(String contextCode, String userQuery, ImmutableArray1 selectionRanges, IReadOnlyList1 definitionContext, CancellationToken cancellationToken, Boolean useEmbeddedRanking) in D:\a_work\1\s\src\Copilot.CodeIndex\Infrastructure\Context\ContextRankingManager.cs:line 77
at Microsoft.VisualStudio.Conversations.Service.Indexing.SemanticContextService.GetSemanticContextAsync(String filePath, String code, IReadOnlyList`1 selections, String query, CancellationToken cancellationToken)

Could someone have a serious look at this - it is ongoing and intermittent, and seems to me to be getting worse?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐