-
Notifications
You must be signed in to change notification settings - Fork 22
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
dump_config
doesn't handle all values correctly
#843
Comments
I have also upgraded all packages to the latest versions (including pygls), as far as was possible, but that did not solve the exception. |
dump_config
doesn't handle all values correctly
One of the things that Unfortunately, it looks like it found something it couldn't handle correctly
From the error, I'm not entirely sure where the issue is... but I'm guessing you a regular expression somewhere in your |
In
When I disable this statement and restart VS Code, the error goes away and the Esbonio HTML preview is working. |
Great, thank you for the example option |
Hi, I tried the new Esbonio pre-release v0.95.0, but unfortunately I still get the same error. Here is my new logfile:
|
@alcarney Or should I create a new issue? |
No it's fine we may as well use this one |
Huh, I am surprised it's still an issue, the example option you shared above is now part of the
This is a bit of a long shot, but if you enable I'm wondering if Sphinx could still be using the old version of the code |
We have a script to clear (remove) the build directory. That's another thing I was wondering about; when I try to delete the
If I try to delete it in Windows Explorer, it says Unfortunately the BTW: We have multiple regular expressions in our |
I have stripped my For what it's worth, my current list of installed pip packages is:
|
Ah, I always forget Windows does not let you delete open files 😅
One option would be to rework the server so that it does not keep a persistent connection open to the I picked the build directory simply because it felt natural and it's clear which project they're associated with - I don't suppose you have any thoughts on what an alternative could be?
About that... for some reason the release build for |
Haha, yes, Windows is very picky about this. If it only would tell who/what opened a file. In this case it's referring to Python, but most of the times it just says something like 'cannot complete operation, file is opened by another process'. Not annoying at all 😅
Yes, I agree, storing them outside of
Yes, I thought so that was the reason. I have created a new issue and expressed my thoughts in it: #865
Yes, thank you, now it works! |
Expected behavior
Have a working preview function with prerelease version 0.94.2 of Esbonio.
Actual behavior
Got an exception instead.
Log output
(Optional) Settings from conf.py
No response
The text was updated successfully, but these errors were encountered: