Skip to main content

Running a fully local AI Code Assistant with Continue–Part 6–Troubleshooting

In a previous posted I introduced you to Continue in combination with Ollama, as a way to run a fully local AI Code Assistant.

Remark: This post is part of a bigger series. Here are the other related posts:

Although Continue really looks promising, I stumbled on some hurdles along the way. Here are some tips in case you encounter issues:

Tip 1 - Check the Continue logs

My first tip is to always check the logs. Continue provides good logging inside the IDE, So go to the output tab and switch to the Continue source to get the generated output:


Tip 2 – Check the Continue LLM logs

Next to the output of Continue itself, you can find all the LLM specific logs in the Continue LLM Prompt/Conversation output. So don’t forget to check that output as well:

Tip 3 – Be patient

When executing a heavy operation, like for example indexing a documentation website, be aware that this can take some time. While such a heavy operation is in progress, continue doesn’t give much feedback what could make you think that the action failed.

So be patient and just wait a little longer…

Tip 4 – A restart can help

While using Continue I noticed that a change didn’t immediately had effect. For example, adding a new document source or adding a new custom command. In that case, just restarting VS Code helped a few times.

So give it a try…

Tip 5 – Check the config.json file

There are a lot of things that can be configured and tweaked inside Continue.

So the config.json file is the go to place. Therefore hit ctrl+shift+p and choose Continue: open config.json.

 

Now you can see all the configuration details and start tweaking them(don’t forget tip 4 and restart VS Code after doing your changes).

Tip 6 – Use the Developer Console to get more details

As a last resort, you can check the developer console logs of VSCode. Therefore hit ctrl+shift+p and choose Developer: Toggle Developer Tools.

Here you can go to the console tab and view all the log messages:

Remark: Change the log level to Verbose by clicking the dropdown at the top that says "Default levels" and select "Verbose".

Hope that helps!

More information

Troubleshooting | Continue

config.json Reference | Continue

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more