You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am reporting a very elusive and hard-to-reproduce issue.
While using ipdb.set_trace() inside https://github.com/isaac-sim/IsaacLab (with docker), I discovered that the debugger hard breaks if used inside the simulation loop (e.g. simulation app is launched and running). Regular pdb does not have such issues.
After some tracing, I figured that parsing of promts by Ipython/terminal/debugger.py somehow returns Nonehere. This line essentially relies on PromptSession.promt() of python-prompt-toolkit, here.
After downgrading to prompt-toolkit==3.0.36 the issue went away.
So,
this combination of ipython with promt_toolkit does not work
ipython==8.26.0
prompt_toolkit==3.0.47
but this one does
ipython==8.26.0
prompt-toolkit==3.0.36
I am fully aware that this an awful bug report, as it is not reproducible without running some 3rd party tools in a docker. But at least it's some documentation of the issue.
The text was updated successfully, but these errors were encountered:
I am reporting a very elusive and hard-to-reproduce issue.
While using
ipdb.set_trace()
inside https://github.com/isaac-sim/IsaacLab (with docker), I discovered that the debugger hard breaks if used inside the simulation loop (e.g. simulation app is launched and running). Regularpdb
does not have such issues.After some tracing, I figured that parsing of promts by
Ipython/terminal/debugger.py
somehow returnsNone
here. This line essentially relies onPromptSession.promt()
ofpython-prompt-toolkit
, here.After downgrading to
prompt-toolkit==3.0.36
the issue went away.So,
this combination of
ipython
withpromt_toolkit
does not workbut this one does
I am fully aware that this an awful bug report, as it is not reproducible without running some 3rd party tools in a docker. But at least it's some documentation of the issue.
The text was updated successfully, but these errors were encountered: