Skip to content

Prevent StatusLine from SWT Invalid thread access #2792

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

Conversation

mickaelistria
Copy link
Contributor

Since monitor methods may be invoked from any thread, make sure we wrap all SWT operations in UI Thread.

Fixes eclipse-jdt/eclipse.jdt.core#3718

@mickaelistria
Copy link
Contributor Author

ProgressDialog would also deserve to be fixed together with this change.

Copy link
Contributor

github-actions bot commented Feb 12, 2025

Test Results

 1 824 files  ±0   1 824 suites  ±0   1h 35m 0s ⏱️ + 2m 24s
 7 918 tests ±0   7 690 ✅ ±0  228 💤 ±0  0 ❌ ±0 
23 841 runs  ±0  23 093 ✅ ±0  748 💤 ±0  0 ❌ ±0 

Results for commit 1319d28. ± Comparison against base commit 73ea7e9.

♻️ This comment has been updated with latest results.

Since monitor methods may be invoked from any thread, make sure we wrap
all SWT operations in UI Thread.

Fixes eclipse-jdt/eclipse.jdt.core#3718
@akurtakov akurtakov force-pushed the statusline-uithread branch from a01c7f7 to 1319d28 Compare April 22, 2025 06:31
@akurtakov
Copy link
Member

Do you plan to get this one finished?

@mickaelistria
Copy link
Contributor Author

This one is currently insufficient (see my last comment about ProgressDialog) and the initial user story behind it is very low priority. Let's abandon for now.

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.

PlainJarExportTests test fails due the monitor use in wrong thread
2 participants