-
Notifications
You must be signed in to change notification settings - Fork 188
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
Disable UI Freeze Error log by default #2218
Labels
enhancement
New feature or request
Comments
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Aug 26, 2024
…atform#2218 As it is counterproductive to pop up error log when something took too long. eclipse-platform#2218
IMHO this change is fine. The period in which I hoped that all long operations will run out of the UI thread has passed, looks like this expectation was unrealistic. I would not do this shortly before the release , better to wait for a new release cycle. |
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Aug 26, 2024
…atform#2218 As it is counterproductive to pop up error log when something took too long. eclipse-platform#2218
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Sep 5, 2024
…atform#2218 As it is counterproductive to pop up error log when something took too long. eclipse-platform#2218
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Sep 5, 2024
…atform#2218 As it is counterproductive to pop up error log when something took too long. eclipse-platform#2218
jukzi
pushed a commit
that referenced
this issue
Sep 5, 2024
As it is counterproductive to pop up error log when something took too long. #2218
lathapatil
pushed a commit
to lathapatil/eclipse.platform.ui
that referenced
this issue
Oct 21, 2024
…atform#2218 As it is counterproductive to pop up error log when something took too long. eclipse-platform#2218
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When something takes long it is contra productive that the error log pops up and robs the focus, disturbing my work even more. It should do so on real errors, but some things simply take long. Therefore by default the error log should only pop up on errors and freezes should not be reported as errors.
Downgrading freezes error/warning to warnings/info does not work so good with public API likeorg.eclipse.ui.monitoring.PreferenceConstants.LONG_EVENT_ERROR_THRESHOLD_MILLIS
WDYT?
The text was updated successfully, but these errors were encountered: