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.

Sign up for GitHub

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

surface runtime errors in code #31

Closed
3 of 5 tasks
pelikhan opened this issue May 6, 2016 · 5 comments
Closed
3 of 5 tasks

surface runtime errors in code #31

pelikhan opened this issue May 6, 2016 · 5 comments
Assignees
@pelikhan
Labels
blocks editor enhancement far out monaco editor Wont Fix and Revisit Later

Comments

@pelikhan
Copy link
Member

pelikhan commented May 6, 2016 •
edited

An API that allows the runtime (simulated or hardware) to surface a runtime issue in the code editor. We had a simular feature in TD.

  • message passing support for surfacing messages from simulator or debugger interface
  • API to report an error
  • walk the stack back under the first user frame is found
  • display in javascript editor (Sam)
  • display in block editor (peli)
@mmoskal
Copy link
Member

mmoskal commented May 12, 2016

We should also consider breaking into a debugger on crash.

mmoskal added a commit that referenced this issue Sep 2, 2016
@mmoskal
Add pxtrt::runtimeWarning with handling; see #31
1958df7
@mmoskal
Copy link
Member

mmoskal commented Sep 2, 2016

The editor support needs to be added. We may also need some throttling somewhere.

@mmoskal mmoskal assigned pelikhan and unassigned mmoskal Sep 2, 2016
mmoskal added a commit to microsoft/pxt-microbit that referenced this issue Sep 2, 2016
@mmoskal
Add pxtrt::runtimeWarning() support; see microsoft/pxt#31
e0de55d
@pelikhan pelikhan assigned samelhusseini and pelikhan and unassigned pelikhan Sep 2, 2016
@tballmsft
Copy link
Contributor

We have this, sort of, right now, with highlighting of line where error occurred, but it's not optimal.

@abchatra
Copy link
Contributor

won't fix for now

@lock
Copy link

lock bot commented Sep 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pelikhan pelikhan

Labels
blocks editor enhancement far out monaco editor Wont Fix and Revisit Later
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@pelikhan @abchatra @mmoskal @tballmsft @samelhusseini