-
Notifications
You must be signed in to change notification settings - Fork 344
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
[Gauge 1.5.6][Python][Debugging] PDB automatically raise BdbQuit #2424
Comments
@bockstaller do you think it's possible we might need for gauge-python to have its own special approach here (as you noted gauge-ruby has?) |
It might, I'll take a look |
I am afraid you are correct @chadlwilson My guess without logs: |
Here is the info of gauge with gauge -v: Gauge version: 1.5.6
|
Ok, this looks like my suspicion is true. |
I tried with "Debug Scenario" function, and noticed that this issue did not occur with vscode breakpoints |
Does using "Debug Scenario" or using gauge version 1.5.5 solve your immediate problem? @chadlwilson if this is the case, I would take a look at switching the lsp communication channel away from stdio and revert the stdin change in common instead of introducing more special cases. |
@bockstaller |
I'm not sure I know enough about LSP to know the right way forward here. Maybe @sriv or @zabil or @haroon-sheikh have an opinion? |
I am not very well versed in the python stack, but a cursory look tells me that Short of that, we may need to switch using pipe or socket as jsonrpc transport. |
I'm afraid the project doesn't have the necessary contributors and knowledge to prioritise this without further outside help. I guess we implicitly decided fixing the wider vscode issues with the language server (especially typescript usage) were higher priority than continued confidence in debugging via PDB or other plugins relying on stdio - which is unfortunate, but probably unavoidable given the current maintenance situation. :-( |
Any updates? |
Describe the bug
When using pdb.set_trace(), Python-PDB automatically raise BdbQuit when meet the breakpoint.
It occurs with gauge 1.5.6, and does not occur with 1.5.5
The text was updated successfully, but these errors were encountered: