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

Gitlab Duo Chat is not returning any output #20280

Closed
j0nes2k opened this issue Oct 9, 2024 · 2 comments
Closed

Gitlab Duo Chat is not returning any output #20280

j0nes2k opened this issue Oct 9, 2024 · 2 comments
Labels
meta: stale This issue/PR is stale and will be closed soon team: team-experience type: bug Something isn't working

Comments

@j0nes2k
Copy link

j0nes2k commented Oct 9, 2024

Bug description

Gitlab Duo Chat is not returning any output in Gitpod

Steps to reproduce

  • create a repository on gitlab.com (or fork below)
  • access this repository using gitpod.io
  • install the Gitlab VSCode Extension there
  • create a personal access token using api, read_api, read_user, read_repository, ai_features, add this to Gitpod environment variables
  • open Gitlab Duo Chat, say "hello"

Results:

  • No answer is posted in the Gitpod VSCode Duo View. However I can see the posted query by accessing Duo via the gitlab.com web interface.
  • the prompts seem to be transmitted to Gitlab, as I can see the queries on gitlab.com
  • other features of the Gitlab VSCode extension work fine (like checking pipeline status etc)
  • everything works as designed when using the Gitlab WebIDE
  • I have Gitlab Premium as well as the Duo Pro addon trial

Workspace affected

No response

Expected behavior

Chat answers inline in VSCode using Gitpod

Example repository

https://gitlab.com/j0nes2k/gitlab-duo-vscode-bug

(Pretty empty, but sufficient)

Anything else?

No response

@j0nes2k j0nes2k added the type: bug Something isn't working label Oct 9, 2024
@axonasif
Copy link
Member

Something small might not be working as as should. Could you try from VS Code Desktop as well?

Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the meta: stale This issue/PR is stale and will be closed soon label Jan 27, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon team: team-experience type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants