-
Notifications
You must be signed in to change notification settings - Fork 88
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
sectionFinder error thrown when trying to render #203
Comments
@iansan5653 thanks for submitting an issue! Sorry to hear about the issues you are encountering, the extension locking up your vscode is not the intention, heh. Lets try to diagnose the problem...
|
Sorry, I've been out of the office this week. I am still able to replicate the error, even after updating all extensions today. Here are my responses:
I noticed today that the error doesn't always appear immediately. Today, when I was editing
When I switched to a project file, this was added:
|
Actually, there is one improvement - it doesn't seem to lock up all the other extensions on failure now. |
@iansan5653 thanks for the extra info, I will try to look into this within a week. |
@iansan5653 I started looking into this but couldnt find anything obviously wrong but one thing of note is that those errors (more like warnings in this case) are caused by the filename / path not resolving to an absolute value (https://gist.github.com/iansan5653/c6dc8b0d2a79249d9f2b87a8539a01ea#file-cov-xml-L45 vs https://github.com/ryanluker/vscode-coverage-gutters/blob/master/example/python/cov.xml#L19). This by itself shouldnt cause the other coverages to not be shown and you did confirm that the example python project works fine. Lets try a few more things...
|
Had the same problem and using: "coverage-gutters.ignoredPathGlobs":
"**/{node_modules,venv,vendor,.tox,.pytest_cache,__pycache__}/**", did the trick for me. |
Hi. pipenv user here. Same issue:
For me should ignore something like:
|
Trying it after running
They keep going like that for a while. |
I am not using pipenv (or any virtual environments) by the way. |
Any updates? I really miss this feature. |
@iansan5653 I am getting back into putting some more time into this project so I will investigate this a bit again today. |
Misc cleanup of definitions and coverage parser system
@s-weigand @iansan5653 might have figured out how to fix this, please try out the vsix below and let me know how it works! |
closing this as it will go out with the next release, thanks again for submitting an issue! |
When I click the "Watch" button, the extension runs until it outputs the following error message:
At this point, all extensions in VSCode stop working until I reload the program.
All of my settings for the extension are stylistic:
Here's my system info:
Version: 1.31.0-insider (user setup)
Commit: 344f4fa361e098b49aeace9602e89275fbbd17bf
Date: 2019-01-10T06:21:21.472Z
Electron: 3.0.13
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.15063
I am happy to provide more information, but I am not sure what is relevant. My coverage file is kept in the project root as
cov.xml
, and this project does have modules and submodules with__init.py__
files.The text was updated successfully, but these errors were encountered: