Troubleshooting guides
This page gathers the common configuration issues met when using the Packmind plugins.
Last updated
Was this helpful?
This page gathers the common configuration issues met when using the Packmind plugins.
Last updated
Was this helpful?
If you've plugged a custom AI provider with Packmind, such as , you'll need to take into considerations the following points:
The AI consumption will depend on the number of practices imported and passed through the program generation step, to detect their violations. The frequency of these two operations will depend on the size of your organization that uses Packmind.
From experiences with our customers, we noticed that a low "query rate/minute" and a low "tokens input/minute" can cause troubles with Packmind. For both practice import and program generation use cases, Packmind uses AI workflows that may up to 15/20 requests to your AI providers per minute, depending on the LLM latency.
We'd recommend to allow:
Up to 50 requests par minute
Up to 2,000,000 input tokens and 500,000 output tokens
However, if you care about setting rate limits, we advise to instead set daily or hourly limits, as the Packmind use cases are not intended to run continuously, but more occasionally.
When extracting coding practices from , you may encounter some runtime issues in the logs, such as a 403:
This might be related to permissions issues, for instance because your token has expired or has not anymore the required permissions. Please check that the current token permissions are appropriate based on your .
You might face occasional errors with the Packmind IDE plugin:
Your API Key is not configured correctly : To ensure you've got the right API Key, go to the Packmind web app, in the Account -> API Keys and Addons" section, and make sure to copy/paste your API key in the your IDE settings.
Can't reach server : This means the Packmind server (Cloud or Self-Hosted) cannot be reached from your IDE, probably because it's currently down or inaccessible. Please check the Packmind web application to check if the server is up and running.
In case the application is fine but you still face an error in your IDE, it's maybe because your API Key embeds a misconfigured Packmind URL. Check with a Packmind admin to ensure that the Packmind URL is properly configured.
Invalid response type: check with your administrator for proxies configuration : This error comes when the Packmind IDE plugin gets responses in an unexpected format. Some customers experienced this when the requests met some HTML content such as a SSO login page or even a CATCHA page. In most cases, it means the response won't come from the Packmind server but from an intermediate entity.
If you use the Packmind Cloud version, some security settings may block the network connection between your IDE and the Packmind API.
If that happens, contact the security admin in your organization and ask for whitelisting Packmind with the following information:
Here are the current addresses ranges Packmind may have as an outgoing IP:
CNAME
This error usually happens when the URL of Packmind, which is part of the API Key, doesn't match the actual Packmind url.
You should check either the PROMYZE_URL environment variable, or go in the Administration -> Configuration menu to check the Packmind available, and check if it's correct or not.
If you get an error containing the following message:
That means you probably need to import the Packmind certificate into your JVM (the one running your IDE).
This operation is the same for Packmind Cloud or On-Premise and can be achieved through your Web browser:
After this step, you'll get a .cer file.
In IntelliJ, Help -> Find Action -> Choose Boot Runtime for the IDE.
Note the name of the Java version that is displayed.
Open a Powershell terminal, and go to your Java installation directory, in the "bin" directory. For instance:
Then, this is the command to import the certificate, replace "packmind.cer" with the full path of the previously exported certificate, and the full path of the "cacerts" file.
You'll likely be prompted with a password. By default, the keystore password is changeit.
Once the certificate has been added, you can now reboot your IDE, and that should solve the issue!
The Packmind plugin for web browsers works only on Pull/Merge Request reviews page for Gitlab, Github, Bitbucket, and Azure DevOps.
It's not intended to work for other pages or other platforms.
If you need more information, directly.
If the problem is still not solved, directly.