-
Notifications
You must be signed in to change notification settings - Fork 2
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
Getting timed out on fresh odoo install #29
Comments
Thanks for the issue! You can specify Also would you mind sharing how you lay out your Odoo modules? odoo-lsp is known to cause issues when scanning a folder containing multiple versions of Odoo, and the information might also help improve odoo-lsp for other users as well. Thank you! |
Should be resolved by a16fda9 |
Hello, sorry for the late reply!
Thanks, turns out you've gotta put neovim after that, for some reason I didn't do that
Looks a bit like this
E is my root drive, ignore the fact that the folder is called Unfortunately it doesn't appear to have solved the problem entirely. It appears to work on XML Views just fine: But not on python, weirdly: Both examples are from CRM, the XML one is from crm/views/calendar_views.xml, the python one is from crm/models/calendar.py It also appears to lock or freeze when indexing, however thankfully this doesn't stop code completion most of the time Here are the logs for the last few sessions, I've enabled debug for extra verbosity and it appears that there are a lot of errors happening, though it seems as though rust's formatted error messages do not play nicely with neovim's logging: Logs
|
Thanks for the note. You should be able to specify the envvar |
After some more testing, I found it to be quite inconsistent in where it works. Sometimes it works on python, sometimes it doesn't work on XML, sometimes they both work, sometimes they both don't. I have no clue why this is happening, but I can give some more readable logs Logs of session where XML doesn't work
Logs where Python works and XML doesn't work (incomplete completion options)
|
If I had to guess why this happens, I'd say that it might be a problem with the indexing causing it to block on some modules, as I noticed that the indexing info you see on the status bar seemed to be stuck indexing some modules Since you said that previously it was single threaded, a block in the indexing would cause everything to block and completion to fail entirely, which was what happened. After switching to multi-threaded, completion sometimes works but is incomplete, which might be caused due to incomplete indexing as it was blocking in certain modules This is just a guess however, it could be something entirely different, but I think it might be caused by something going wrong in indexing |
It was observed during local testing with nvim (WSL2) that diagnostics are requested very early into the process without waiting for initialization, which could have caused a deadlock. 7c6cdc8 should hopefully fix this, which is now in nightly-20240827. |
Firstly, sorry for the late reply, again. Secondly, it seems as though this unfortunately hasn't quite solved the issue It also appears that it isn't a problem specific to my specific installation of odoo I've been using, as I've installed it again and still experienced the same bugs Here are the logs from my latest session, which I've been running for at least 4 minutes and, at the time of writing, is still stuck on
|
Unfortunately after further testing it appears as though that hasn't solved the problem, and is still freezing while indexing I also noticed that it produced a copious amount of errors. So, I tried changing my python LSP (formerly Pyright) to something else (pylsp), however it appears as though that hasn't solved the problem Here is the log file from the most recent session (using pylsp):
On a related note, you seem to be using neovim for your demos on your readme. Would you mind sharing me your LSP configuration? |
@myname1111 Unfortunately I'm not daily driving nvim right now, the demos are done in Helix where most of the issues have relatively subsided. There is the init.lua which just hooks up odoo-lsp with lspconfig, which I believe you might already be doing. |
In that case I'll try to see if this bug appears on helix as well when I have time |
I'm getting a timed out error on a fresh odoo source install when looking at my log files, it appears that the lsp works for a little while before getting stuck on a certain module, what module that is doesn't appear to be consistent, for my latest session that module is 'web_editor'. I'm not sure why but it seems like it is incapable of loading the entire odoo source, which seems reasonable, so I'm guessing it's supposed to load just a single module? but I'm not sure that's your intention with this guessing from the .odoo_lsp files and how they seem to imply that this is supposed to load the entire source
Here are the log files for today:
I'm also unable to enable debug logs for odoo-lsp, apparently there's a syntax error or maybe I'm not replacing some sort of placeholder, I'm not sure, would you mind helping me with this too?
Extra information:
Here is a compressed version of my version astrolsp.lua (where I setup my lsp configs and settings):
The text was updated successfully, but these errors were encountered: