pytest timeout respected when breakpoint is hit
@eleanorjboyd is already working on this.
Since Oct 28, 2024.
Assessment
This issue has not been assessed yet.
Description
At the Home Assistant core repo, we use this extension to debug pytest unit tests. There's a 10 seconds timeout passed to pytest.
Prior to v2024.11.2024092501, when a breakpoint is hit, the breakpoint remains hitted until the users acts (continue to debug, step in, any action). With v2024.11.2024092501, the timeout seems to be respected somehow and the breakpoints is no longer hit around 10 seconds after starting.
Reproduction steps:
Open a devcontainer of https://github.com/home-assistant/core
Ensure the latest python-debugger is installed
Change a test (add a random assert), place a breakpoint on this assert
Go to "Run and debug" and choose "Home Assistant: changed tests"
See the breakpoint being hit, wait 10 seconds, breakpoint is no longer hit
- Dominant language
- TypeScript
- Stars
- 181
- Forks
- 126
- Avg merge
- 8h 49m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-python-debugger
-
triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/vscode-python-debugger#1110 ·
-
triage-needed
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
microsoft/vscode-python-debugger#1024 · 1 comment ·
-
triage-needed
microsoft/vscode-python-debugger#1111 · 1 reaction · 1 assignee ·
-
triage-needed
microsoft/vscode-python-debugger#1104 · 1 reaction · 1 assignee ·
-
triage-needed
Difficulty 4/5 3-5 days Newbie friendliness 58/100
microsoft/vscode-python-debugger#1095 · 1 comment · 1 reaction ·
All issues in microsoft/vscode-python-debugger
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 88/100