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

Don't let the IDE throw away executionContext/executionStatus messages #5734

Conversation

JaroslavTulach
Copy link
Member

Pull Request Description

IDE currently completely ignores executionContext/executionStatus messages without giving user any clue - even if the reported status signals an error.

Important Notes

Checklist

Please include the following checklist in your PR:

  • The documentation has been updated if necessary.
  • All code conforms to the
    Rust
    style guides.
  • All code has been tested:
    • Unit tests have been written where possible.
    • If GUI codebase was changed: Enso GUI was tested when built using BOTH
      ./run ide build and ./run ide watch.

Comment on lines +173 to +177
/// Any message to be displayed as a notification
Message {
/// text of the message
message: String,
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not needed, we already have such notifications in

pub enum StatusNotification {

Copy link
Contributor

@farmaazon farmaazon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think sometimes this solution can rather confuse user than help him:

  1. The errors reported in the execution status are still not displayed if warning happens to be first on the list
  2. We do not inform the user about the place where error is produced. Theoretically it could be in the different file

Overall, I'd prefer to implement #5201 first, then make it properly: display a message with details section, and in details print all the information we get in executionStatus message.

The error log could remain. But then, let's print errors for all messages.

@JaroslavTulach
Copy link
Member Author

Original problem addressed by #5794. Closing.

@farmaazon farmaazon deleted the wip/jtulach/DontThrowAwayExecutionStatusMessages_5260 branch May 9, 2024 07:40
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

Successfully merging this pull request may close these issues.

Throwing an unhandled exception in Polyglot Java results in a null in the UI and no caught error message
2 participants