Community
Participate
Working Groups
In 2019-06 I am finding that the error/warning squiggles are often inconsistent and do not update at all. Previously there was sometimes a one/two second lag, but eventually they appeared.. e.g. the following function within org.eclipse.qvtd.xtext.qvtrelation.tests.QVTrCompilerTests contains a double error as a consequence of a partial edit. protected void checkLoadability(@NonNull URI testURI) { OCL ocl = OCL.newInstance(getTestProjectManager()); Resource resource = ocl.getResourceSet().getResource(testURI, true); assertNoResourceErrors("Load " + testURI, qvtsResource); assertNoUnresolvedProxies("Load " + testURI, qvtsResource); ocl.dispose(); } No errors are shown until the file is saved at which point the correct red squiggles occur under the two "qvtsResource" references that have yet to be changed to "resource". While the errors are missing, hovering over "qvtsResource" gives no hovertext to explian where the 'satisfactory' definition is.
After saving and then editing to remove the errors hovering over the corrected "resource" text gives the usual popup to the effect that "qvtsResource" cannot be resolved to a variable. It seems the in-memory incremental compilation is not happening.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Cannot be stale till triaged by a relevant committer.
