When exception is raised, the "Current traceback" window is empty #429
Comments
|
I'm seeing the same issue. I'm on Ubuntu 23.10 using miniforge: |
|
Quick fix for this: diff --git cq_editor/widgets/traceback_viewer.py cq_editor/widgets/traceback_viewer.py
index d5e0baa..4b1043d 100644
--- cq_editor/widgets/traceback_viewer.py
+++ cq_editor/widgets/traceback_viewer.py
@@ -56,6 +56,6 @@ class TracebackPane(QWidget,ComponentMixin):
root = self.tree.root
code = code.splitlines()
- tb = [t for t in extract_tb(tb) if '<string>' in t.filename] #ignore highest frames (debug, exec)
+ tb = [t for t in extract_tb(tb) if 'string>' in t.filename] #ignore highest frames (debug, exec)
for el in tb:
#workaround of the traceback module |
smurfix
added a commit
to smurfix/CQ-editor
that referenced
this issue
Apr 8, 2024
Also trace into external modules. Closes CadQuery#429.
Merged
|
I opened PR #431 with a better fix that doesn't suppress tracebacks in called modules. They're too helpful for finding the actual problem … |
adam-urbanczyk
added a commit
that referenced
this issue
Jun 4, 2024
* Show the traceback. Also trace into external modules. Closes #429. * Use itertools for clarity * Cleanup * Remove empty line * Cover new functionality with tests --------- Co-authored-by: AU <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See result when raising `RuntimeError('example').
I need to run the script outside of cq-editor to get the stack trace in console.
I am on Debian, installed cq-editor with micromamba:
The text was updated successfully, but these errors were encountered: