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

Component: Error-Handling #5258

Open
5 tasks
StachuDotNet opened this issue Jan 13, 2024 · 0 comments
Open
5 tasks

Component: Error-Handling #5258

StachuDotNet opened this issue Jan 13, 2024 · 0 comments

Comments

@StachuDotNet
Copy link
Member

StachuDotNet commented Jan 13, 2024

Darklang raises structured RuntimeErrors upon unexpected/invalid operations in execution.
Each runtime (CLI, Cloud, etc) captures these and decides what to do, with some configurability availed to the user.

This issue is to organize work related to Darklang's error-handling and supporting users' efforts towards preventing, diagnosing, and resolving errors.

  • revisit how our existing runtimes handle RTEs
  • consider configurability of handling such
  • consider allowing users to explicitly raise RTEs

Old specific error reports to consider:

  • Got “Unknown error” as a function was throwing an unexpected exception. We hid that exception because we don’t want to show it to grand users, which are not a concern in the CLI
  • Got an error “Both values must be the same type” - but which values? That’s not recorded because we assume it’ll be filled in later via traces. But we don’t have traces (maybe we should, but how?)
@StachuDotNet StachuDotNet added the needs-review I plan on going through each of the issues and clarifying them -- this is to mark remaining issues label Feb 14, 2024
@StachuDotNet StachuDotNet removed the needs-review I plan on going through each of the issues and clarifying them -- this is to mark remaining issues label Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant