Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@workspace error - bad export type for tree_sitter_tsx_external_scanner_create: undefined #1292

Closed
Selyss opened this issue Jun 8, 2024 · 4 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@Selyss
Copy link

Selyss commented Jun 8, 2024

Using @workspace to add context results in an error bad export type for tree_sitter_tsx_external_scanner_create: undefined. This seems to occur when trying to use the context to generate a response. It occurs every time I try and use the service. Screenshot below.

  • VS Code Version: 1.90.0
  • OS Version:

In a codespace:

Distributor ID: Ubuntu
Description: Ubuntu 20.04.6 LTS
Release: 20.04
Codename: focal

  • Logs:
    2024-06-08 14:04:37.066 [info] [fetcher] Using Helix fetcher, Electron fetcher is not available.
    2024-06-08 14:04:37.066 [info] [code-referencing] Public code references are enabled.
    2024-06-08 14:04:37.067 [info] [auth] Sucessfully authenticated

Steps to Reproduce:

  1. Open copilot chat
  2. Create a prompt that adds @workspace context

image

@github-actions github-actions bot added the triage-needed Issues needing to be assigned to the prospective feature owner label Jun 8, 2024
@ulugbekna
Copy link
Contributor

Thank you for filing the issue!

Which version of Copilot Chat are you on?

You can check it by finding the Copilot Chat extension in extension marketplace

Image

@ulugbekna ulugbekna added info-needed Issue requires more information from poster and removed triage-needed Issues needing to be assigned to the prospective feature owner labels Jun 9, 2024
@Selyss
Copy link
Author

Selyss commented Jun 11, 2024

I'm on v0.16.0.

@GarlandKey
Copy link

@Selyss Updating the extension and reloading fixed this error for me.

@mjbvz
Copy link

mjbvz commented Aug 28, 2024

I think this issue has been fixed in the current release. Please let us know if you're still seeing it

@mjbvz mjbvz closed this as completed Aug 28, 2024
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Oct 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

4 participants