Troubleshooting Code Suggestions

Tier: Premium with GitLab Duo Pro, Ultimate with GitLab Duo Pro or Enterprise - Start a trial Offering: GitLab.com, Self-managed, GitLab Dedicated
History
  • Changed to require GitLab Duo add-on in GitLab 17.6 and later.

When working with GitLab Duo Code Suggestions, you might encounter the following issues.

You can run a health check to test if your instance meets the requirements to run Code Suggestions.

Suggestions are not displayed

If suggestions are not displayed, follow these steps:

  1. Ensure you have installed a supported IDE extension
  2. Ensure your administrator has assigned you a seat.

If suggestions are still not displayed, try the following troubleshooting steps.

Suggestions not displayed in VS Code or GitLab Web IDE

If you are a self-managed user, ensure that Code Suggestions for the GitLab Web IDE is enabled. The same settings apply to VS Code as local IDE.

  1. On the left sidebar, select Extensions > GitLab Workflow.
  2. Select Settings (), and then select Extension Settings.
  3. In GitLab > Duo Code Suggestions, select the GitLab Duo Code Suggestions checkbox.

View Code Suggestions logs

If the settings are enabled, but suggestions are still not displayed, try the following steps:

  1. In the GitLab Workflow Extension Settings, enable GitLab: Debug.
  2. On the top menu, select View > Output to open the bottom panel, then either:
    • In the command palette, select GitLab: Show Extension Logs.
    • In the bottom panel, on the right, select the dropdown list to filter the logs. Select GitLab Workflow.
  3. In the GitLab Workflow Extension Settings, clear and re-select the GitLab Duo Code Suggestions checkbox.

Suggestions not displayed in JetBrains IDEs

  1. Ensure you have properly set up the extension.
  2. From the Tools > GitLab Duo menu, select Verify setup. Make sure the health check passes.
  3. Verify that your JetBrains IDE natively supports the language of the file you are working on. Go to Settings > Languages & Frameworks to see the full list of languages and frameworks supported by your JetBrains IDE.

Suggestions not displayed in Microsoft Visual Studio

  1. Ensure you have properly set up the extension.
  2. From the Tools > Options menu, find the GitLab option. Ensure Log Level is set to Debug.
  3. Open the extension log in View > Output and change the dropdown list to GitLab Extension as the log filter.
  4. Verify that the debug log contains similar output: 
14:48:21:344 GitlabProposalSource.GetCodeSuggestionAsync
14:48:21:344 LsClient.SendTextDocumentCompletionAsync("GitLab.Extension.Test\TestData.cs", 34, 0)
14:48:21:346 LS(55096): time="2023-07-17T14:48:21-05:00" level=info msg="update context"

Code Suggestions returns a 401 error

Code Suggestions depends on a license token that synchronizes your subscription with GitLab.

If the token expires, GitLab Duo Code Suggestions returns the following error with status 401 when the token has expired: 

Token validation failed in Language Server:
(Failed to check token: Error: Fetching Information about personal access token

If GitLab has access to the cloud server, try manually synchronizing your license.

Authentication troubleshooting

If the above steps do not solve your issue, the problem may be related to the recent changes in authentication, specifically the token system. To resolve the issue:

  1. Remove the existing personal access token from your GitLab account settings.
  2. Reauthorize your GitLab account in VS Code using OAuth.
  3. Test the Code Suggestions feature with different file extensions to verify if the issue is resolved.