vscode-coverage-gutters: Error Failed to parse string
I’m always getting this error when i try to use the extension. I tried adding the watch on lcov.info and cobertura-coverage.xml, but the error is the same and nothing get displayed on the source code.
Here is the screenshot of the extension output:

About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 41 (23 by maintainers)
Commits related to this issue
- [#150] Refine error handling inside parsers — committed to ryanluker/vscode-coverage-gutters by ryanluker 6 years ago
- Don't crash if we find empty lcov.info (#150) Sometimes we may encounter an empty `lcov.info` file. Since we know that an empty file can't contain valid coverage data, we simply ignore it rather than... — committed to ermshiperete/vscode-coverage-gutters by ermshiperete 5 years ago
- Don't crash if we find empty lcov.info (#150) Sometimes we may encounter an empty `lcov.info` file. Since we know that an empty file can't contain valid coverage data, we simply ignore it rather than... — committed to ermshiperete/vscode-coverage-gutters by ermshiperete 5 years ago
- Merge pull request #215 from ermshiperete/master Don't crash if we find empty lcov.info (#150) — committed to ryanluker/vscode-coverage-gutters by ryanluker 5 years ago
@Licen-it sweet this one is finally fixed, thanks for running the (almost 8 month long) marathon with me 😆 ! You can modify where the coverage is displayed by turning off and of some settings, by default it is just the gutters but you can had the coverage show up inline and on the edges.
@ryanluker i’m getting the same error i mentioned in my comment above and still no gutters showing the code coverage.
@Licen-it thanks for the continual assistance on this one, looks like @DW8Reaper has a new fix (https://github.com/ryanluker/vscode-coverage-gutters/pull/191) that may also help with your issues. I will message again once I have a new 2.3.0 pre-release for you to try.
@Licen-it thanks for submitting an issue! this is related to the score logic that was added recently and should be fixed in the next version of the extension I am working on (2.1.0). In the meantime you could try just loading lcov.info to see if that will help you til next release.