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

Jump to bottom

Make internal MicroPython errors less intimidating #1799

Closed
aivarannamaa opened this issue May 2, 2021 · 0 comments
Closed

Make internal MicroPython errors less intimidating #1799

aivarannamaa opened this issue May 2, 2021 · 0 comments
Labels
MicroPython
Milestone
4.0.0b1

Comments

@aivarannamaa
Copy link
Member

Quite often the fault is on MicroPython (#1788).

Move details to log and keep Shell output cleaner.
@aivarannamaa aivarannamaa added this to the 4.0.0 milestone May 2, 2021
aivarannamaa added a commit that referenced this issue May 2, 2021
@aivarannamaa
Make internal MicroPython errors less intimidating, #1799
5fcccdd
aivarannamaa added a commit that referenced this issue May 2, 2021
@aivarannamaa
Shell doesn't need to show toplevel error
6619f1d 
Assuming the back-end already did it, #1799
@aivarannamaa aivarannamaa modified the milestones: 4.0, 4.0.0b1 Nov 17, 2021
aivarannamaa added a commit that referenced this issue Feb 5, 2022
@aivarannamaa
Simplify MicroPython error presentation, #1799
0e1426c
aivarannamaa added a commit that referenced this issue Feb 5, 2022
@aivarannamaa
Stop the back-end when an uncaught exception escapes handle_normal_co…
bdf903c 
…mmand, #1799
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
MicroPython
Milestone
4.0.0b1
Development

No branches or pull requests
1 participant
@aivarannamaa