Replies: 2 comments
-
|
OK, I think it is due to the following code in protected void schedule(InternalJob job, long delay) {
withWriteLock(job, j -> {
if (scheduleInternal(job, delay, false)) {
pool.jobQueued();
}
return (Void) null;
});
}If the job is scheduled then |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear RAP team,
I currently face the problem that with RAP 3.29.0 the following exception occurs
due to passing a
nullvalue for the progress monitor to a job.I think this is somehow related to
JobManagerAdapter.scheduledorg.eclipse.rap/bundles/org.eclipse.rap.ui.workbench/Eclipse UI/org/eclipse/rap/ui/internal/progress/JobManagerAdapter.java
Line 151 in 28474ab
which is indirectly called from a background thread in
org.eclipse.core.internal.jobs.Worker.run().Therefore the
displaycannot be found as there is no context registered andContextProvider.hasContext()returnsfalse.Is this a known problem or am I doing something wrong?
Best regards,
Ken
Beta Was this translation helpful? Give feedback.
All reactions