Goto next problem does not go in sequence in certain scenarios

[safield]

Version: 1.51.1
Commit: e5a624b
Date: 2020-11-10T23:31:29.624Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.4.0-53-generic

I have observed a scenario where pressing F8 to go to next problem will take me back the first problem, instead of to the next problem.

The problems in my problems view can be summarized as follows. (number of files and issues within files is irrelevant).

File A
problem 1
problem 2
problem 3
File B
problem 1
problem 2
problem 3
File C
problem 1
problem 2
problem 3

-press F8 to go to problem A1.
-keep pressing F8 until you get to problem B3 (the last problem in a file that has problems in a file before it and problems in a file after it).
-fix the problem and save the file.
-press F8 again....
-it jumps to problem A1.

Expected Behaviour
-it should jump to problem C1.

[jrieken]

@sandy081 pretty sure that you are owning these things now

[safield]

This is not a feature request......this is a bug! I did not take the time to compose a well written bug for you, just for your useless bot to close because people are not upvoting. What kind of degenerate dev team is running the show here???

[jrieken]

I did not take the time to compose a well written bug for you

Then do so!

[Spongman]

I have the same issue. making changes to a file in the problems list causes f8 to sometimes restart at the beginning. obviously this is pretty frustrating if you're working serially through a long list of issues.

btw: i agree with the above comment regarding the triage bot. i know it's an attempt to handle the large volume of incoming issues, but really it comes across as "we care so little about your attempts to communicate an issue in our product that we have a robot to automatically trash your input."

[Spongman]

there's also a related issue: if, for whatever reason, f8 needs to pop up the 'Unable to open' popup, it should just skip that issue and move to the next. should i open a new issue for this, or is it the same bug?

[jrieken]

still no repro steps here

[safield]

still no repro steps here

Repro steps are in the initial bug. Why is this closed? Do you guys avoid fixing bugs by pretending they don't exist?

[Spongman]

closing issues due to lack of recent activity is bad program management. bugs should either be closed because they're not bugs, or they're fixed.

[VSCodeTriageBot]

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!