The plugin can't step anymore, starting at vs code 1.79 (May 2023 release).
Plugin version 0.2.3 still works with the latest vs code release. In other words, version 0.3.0 (PR #88) introduced the problem.
@carllocos From a quick debug I couldn't see anything going wrong. I think we may have no other choice than to just try and find the breaking commit with git bisect, even tho its like 400 commits ... (the 100 or so latch commits can be ignored)
But maybe you have some further insight into your code that can narrow it down more?
carllocos
commented
1 year ago
MAJOR ISSUE
The plugin can't step anymore, starting at vs code 1.79 (May 2023 release).
Plugin version 0.2.3 still works with the latest vs code release. In other words, version 0.3.0 (PR #88) introduced the problem.
@carllocos From a quick debug I couldn't see anything going wrong. I think we may have no other choice than to just try and find the breaking commit with
git bisect, even tho its like 400 commits ... (the 100 or so latch commits can be ignored) But maybe you have some further insight into your code that can narrow it down more?