"watch workspace" gets enabled when a file is opened that had been closed when "watch workspace" was enabled

[cswrd]

Describe the bug
Sometimes Coverage Gutters seems to enable itself on its own. I figured out this happens when you open a file that had been closed when the workspace watch was enabled.

To Reproduce
Steps to reproduce the behaviour:

1. Open a source file A and B
2. Enable the Coverage Gutters watch
3. Close file A
4. Disable Coverage Gutters
5. Open the same file A again

Expected behaviour
step 5: Coverage Gutters is still disabled, but gets enabled.

Desktop (please complete the following information):

• OS: Windows 11
• Extension Version v2.10.1
• VSCode Version 1.72.1

[ryanluker]

@cswrd Thanks for the issue, issue bug / issue with the coverage still being applied. Does this only occur with file A in step 5 or would file B also act this way?

[ryanluker]

closing due to inactivity but happen to open again

[cswrd]

Sry for my late answer. Yes it was irrelevant which file was involved. The coverage colors would have been enabled on all files suddenly.

As far as I remember the coverage gutter button in the bottom status bar of VS Code was in an incorrect state when it glitched. It still said "Watch" as if it was not watching, though the code was already coloured.

I tried to reproduce the issue. I am on a different machine now and didn't experience the issue so far:

• OS: Windows 10
• Extension Version v2.10.2
• VSCode Version 1.73.1

I'll let you know if I ever experience it again.