Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes to IW debugging with breakpoints #10263

Merged
merged 4 commits into from
Jun 3, 2022
Merged

Fixes to IW debugging with breakpoints #10263

merged 4 commits into from
Jun 3, 2022

Conversation

DonJayamanne
Copy link
Contributor

Fixes #10258

Will add tests next week.

@DonJayamanne DonJayamanne requested a review from a team as a code owner June 2, 2022 15:39
(bp) => bp.line <= cell.metadata.generatedCode!.endLine
);
}
if (sortedLines.filter((line) => line > cell.metadata.generatedCode!.endLine).length) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rchiodo we add breakpoints for each cell by splitting the breakpoints by cells.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is breakpoints the only thing that needs this special translation? What about stack frames?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's fine

}
// Find the cell that matches this line in the IW file.
const cell = this.cellToDebugFileSortedInReverseOrderByLineNumber.find(
(item) => item.debugFilePath === source.path
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment seems wrong here. It's not searching by line but rather by the translated debugFilePath. That does map to a specific cell entry.

@rchiodo
Copy link
Contributor

rchiodo commented Jun 2, 2022

Tests are actually already there, you just need to undo the changes I made for this issue. Then they'll run the normal tests.

@rchiodo
Copy link
Contributor

rchiodo commented Jun 2, 2022

Oh wait I shouldn't have approved. You should undo the changes I made here:

const debuggerTypes: DebuggerType[] = ['VSCodePythonDebugger'];

and here
// See https://github.com/microsoft/vscode-jupyter/issues/10258

@codecov-commenter
Copy link

codecov-commenter commented Jun 3, 2022

Codecov Report

Merging #10263 (b19749d) into main (fb90ab7) will decrease coverage by 0%.
The diff coverage is 0%.

@@          Coverage Diff          @@
##           main   #10263   +/-   ##
=====================================
- Coverage    64%      64%   -1%     
=====================================
  Files       204      204           
  Lines      9287     9295    +8     
  Branches   1504     1505    +1     
=====================================
+ Hits       5963     5966    +3     
- Misses     2854     2857    +3     
- Partials    470      472    +2     
Impacted Files Coverage Δ
...erminals/codeExecution/codeExecutionHelper.node.ts 31% <0%> (-7%) ⬇️
src/platform/errors/errorHandler.ts 62% <0%> (-1%) ⬇️
src/platform/vscode-path/map.ts 9% <0%> (-1%) ⬇️
src/platform/common/cancellation.ts 66% <0%> (+3%) ⬆️
...rc/platform/common/dataScienceSurveyBanner.node.ts 70% <0%> (+5%) ⬆️

@DonJayamanne DonJayamanne merged commit 6ec5855 into main Jun 3, 2022
@DonJayamanne DonJayamanne deleted the issue10258 branch June 3, 2022 04:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Interactive debugging does not work with ipykernel debugger
3 participants