Errors and Warnings in the status bar show negative count

[sandy081]

• VSCode Version: Insiders
• OS Version: OSX

I am not sure how I got into this state, I was checking out to Master branch from my feature branch. After check out I see this weird state in the status bar.

[dbaeumer]

Without steps hard to fix. If we remove the workaround code that filters resources this might be gone anyways.

[mihailstefanov]

I have same from some time, even in latest version 1.3.1, using Typescript

[dbaeumer]

@mihailstefanov do you have any steps?

[vexxra]

Currently facing the same issue. While I can't provide any steps to reproduce it, maybe some things I noticed might help.

1. The value is not random but a fixed offset. For me it was -15. This means that adding or removing errors to the code updates the value properly. Adding a a a a a a a a to a random line therefore resulted in 0 errors (7 times '; expected', 8 times 'cannot find name 'a''). Funnily enough while messing around I managed to increase this offset to -16, but was unable to change it any further.

2. I think it started after changing a private member to public while still being referenced in another class. Afterwards the reference in the other class randomly claimed that the member is still private, but fixed itself within seconds. The error sort of "flickered" on and off. Could be a coincidence or a side effect though.

EDIT: Happened again today. This time I completely removed a line that had an error in it. This error randomly popped up back again, even though it was long gone. This was acompanied by a negative error count (-2 when no errors appeared, 3 when the error randomly popped up (he popped up 5 times at once)).

Restarting VSCode fixed everything.

[dbaeumer]

What kind of error was it [js], [ts], [eslint], ...

[mihailstefanov]

It is more editor connected.

Regards
Mihail

On Aug 8, 2016, at 1:15 PM, Dirk B?umer <notifications@github.commailto:notifications@github.com> wrote:

What kind of error was it [js], [ts], [eslint], ...

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com//issues/8058#issuecomment-238196067, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFD_giRYSC0UbTW0Fr3ss7WSoDeKgAvzks5qdwG5gaJpZM4I83EU.

[vexxra]

What kind of error was it [js], [ts], [eslint], ...

Sorry, these were [ts] errors.

[dbaeumer]

@stephanjust thanks.

[vexxra]

@dbaeumer I have to correct myself: these errors have no "type" at all. I actually thought that they were [ts] errors based on the content, but as I have this happen at the moment I can see that this is not the case.

While I still have no repro steps to start the entire issue, once it's running I can control it. These errors go away when switching the tab to the file showing the errors, and if not, definitely when changing the content of the file (adding a whitespace is enough). They come back when recompiling the source. Here are two example screenshots showing the change.

[mjbvz]

Closing this as out of date. If you still see this issue, please let us know