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
Exceptions in interactive mode is easy to show as context/shell is alive, not so much with non-interactive. So one options would be to behave differently depending on a mode like printing stacktrace to teminal output on non-interactive. That way user gets useful errors immediately.
The text was updated successfully, but these errors were encountered:
- Change how errors are printed for interactive
vs non-interactive mode.
- This now changes behaviour so that stacktrace is printed
if non-interactive mode is active so that user has a change
to see the full error.
- Fixesspring-projects#427
- Change how errors are printed for interactive
vs non-interactive mode.
- This now changes behaviour so that stacktrace is printed
if non-interactive mode is active so that user has a change
to see the full error.
- Fixes#427
Uh oh!
There was an error while loading. Please reload this page.
Exceptions in interactive mode is easy to show as context/shell is alive, not so much with non-interactive. So one options would be to behave differently depending on a mode like printing stacktrace to teminal output on non-interactive. That way user gets useful errors immediately.
The text was updated successfully, but these errors were encountered: