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
By a glance of the log, I find workDone is 10x larger than totalWork, making status 1000% which is unreasonable. Is it from upstream or set by jdtls itself?
Doing a quick investigation, looks like it's in the CallHierarchyHandler there are some calls to MethodWrapper#getCalls(monitor). We seem to be re-using MethodWrapper calls by caching them as incoming/outgoing. As part of the getCalls(..) logic I see calls to monitor.beginTask(..) which would probably reset the total work (which is what we see). Note that beginTask(..) states Notifies that the main task is beginning. This must only be called once on a given progress monitor instance.
May need to create a monitor subtask before passing it in.
- A method should call Submonitor.convert(..) upon receiving its monitor
in order to correctly allocate its share of the work to be done
- Fixeseclipse-jdtls#1722
Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
- A method should call Submonitor.convert(..) upon receiving its monitor
in order to correctly allocate its share of the work to be done
- Fixes#1722
Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
By a glance of the log, I find
workDone
is 10x larger thantotalWork
, makingstatus
1000% which is unreasonable. Is it from upstream or set by jdtls itself?The text was updated successfully, but these errors were encountered: