Vyacheslav Kovalevsky

Coverage for deploy now seems to be tracked.  There are minor issues with coverage blocks overlapping, though on right (in vscode) you can see red blocks even when overlapped,...

figuring out why tests are failing

Should be fixed. (for some reason `flag.VisitAll` included `coverProfile` flag with value `""`, even when coverage is not enabled in `go test`)

It seems like there are issues with CI coverage, because neotest replaces original coverage data.

 maybe we should use some ENV variable that disables neotest coverage and use it in CI

>  maybe we should use some ENV variable that disables neotest coverage and use it in CI or having a flag would be better?

Naming gets really bad with coverage package, we now have 3 different flags that enable/disable coverage `coverageEnabled`, `isDisabled` + `collectCoverage` in Executor.

do we need this after #18638 merge?

I looked at this closer and it seems like SeqPoints can overlap sometimes (usually one can cover entire function), is this intended?

I guess we would have to actually use AST and maybe keep extra info from codegen