-
Notifications
You must be signed in to change notification settings - Fork 4
Troubleshooting
If you are having issues with the extension not being able to download the binary, try downloading or installing the odoo-lsp binary onto your local PATH, e.g. ~/.local/bin
. The extension will automatically pick up on it, and you can always update the binary using odoo-lsp self-update
.
If for some reason the VSCode extension still can't find odoo-lsp, try passing the absolute path as the SERVER_PATH
environment variable, i.e. SERVER_PATH=<path to odoo-lsp> code ...
.
While efforts are already in place to limit odoo-lsp's memory usage to the minimum while still balancing performance, you can further reduce the memory footprint by passing -j 1
when booting the server, which forces odoo-lsp to use a single core only. Note that this may reduce the responsiveness of the server.
Please don't hesitate to file an issue if you think your workflow should work out of the box, or a Discussion if you are unsure how to use and configure odoo-lsp for your codebases.