Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to disable coverage?

See original GitHub issue

A user cannot disable TLC’s coverage collection, even though collecting coverage data has significant overhead for large-scale model-checking.

https://github.com/alygin/vscode-tlaplus/blob/50bad5f5b0405570435f3c4b107ad2da79fe3a0d/src/tla2tools.ts#L181

My suggestion would be to not set -coverage at all.

Issue Analytics

State:
Created 3 years ago
Comments:13 (6 by maintainers)

Top GitHub Comments

1reaction

klinvillcommented, Aug 14, 2021

We can close this since coverage can be disabled by simply removing the coverage argument from the options prompt introduced in #207. I just re-confirmed that it works in 1.6.0-alpha.2

1reaction

klinvillcommented, Mar 26, 2021

@lemmy is something like this what you were thinking of? I was originally worried about the friction of introducing an extra keystroke every time you want to check a model, but I’m not minding it as much as I thought I would.

https://user-images.githubusercontent.com/6043161/112682061-cf25d380-8e2c-11eb-8478-f78204069102.mp4

Right now I’ve got it keeping track of the last options used in the session, but it reverts to the defaults when a new window is open. I’d rather track the options across sessions, and maybe omit the -config argument from the prompt. That would allow the same options to be used to check different models without needing to explicitly change the -config argument each time. However the -config could still be overwritten from the prompt.