IDE stopped highlighting any errors, tips, anything

This topic contains 10 replies, has 3 voices, and was last updated by  Brian Fernandes 3 months, 1 week ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #578842

    dmitry-b
    Participant

    Hi there,

    At some point (perhaps after last update?) Webclipse Angular IDE has stopped highlighting anything, errors, warnings, lint notes, anything. In such a way it does no longer bring value… as the only point when I can see errors is when lunching “ng serve,” not whilst editing sources.

    Error

    Regards,
    Dmitry

    #578871 Reply

    Brian Fernandes
    Moderator

    Dmitry,

    1)) Go to Window > Preferences > Webclipse – what version is reported here?

    2) When you say you see errors after “ng serve” – I assume you mean in the console / terminal and not in the editor or in the Problems/Markers view?

    3) If you have other files in the workspace, like Java or JS files, do you see errors for those? What about HTML files if you make a HTML syntax error?

    4) Check the Problems and Markers view for to see if issues are reported there but missing from the editor ruler only.

    5) Are there any relevant errors logged? See the Error log view (you can clear it, restart and reproduce the problem to get a more focussed log).

    6) Just as a test, do create a new workspace and import your project into that – does the situation persist?

    Hopefully we can get to the bottom of this asap.

    #578873 Reply

    dmitry-b
    Participant

    Hi Brian,

    1) -> Version

    2) -> Yes.

    3) -> HTML errors are highlighted. That’s Ok. But my main sources are in Angular. I do not edit Java files.

    4) -> Neither problems, nor markers show any issues – that’s a bug.

    5-> There are a couple of exceptions logged following the message “Workspace restored but some problems occurred”:

    org.eclipse.core.internal.resources.ResourceException: The project description file (.project) for ‘qfe’ is missing. This file contains important information about the project. The project will not function properly until this file is restored.
    at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:907)
    at org.eclipse.core.internal.resources.SaveManager.restoreMetaInfo(SaveManager.java:904)
    at org.eclipse.core.internal.resources.SaveManager.restoreMetaInfo(SaveManager.java:884)
    at org.eclipse.core.internal.resources.SaveManager.restore(SaveManager.java:735)
    at org.eclipse.core.internal.resources.SaveManager.startup(SaveManager.java:1587)
    at org.eclipse.core.internal.resources.Workspace.startup(Workspace.java:2399)
    at org.eclipse.core.internal.resources.Workspace.open(Workspace.java:2156)
    at org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:464)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932)
    at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
    at org.eclipse.osgi.container.Module.doStart(Module.java:581)
    at org.eclipse.osgi.container.Module.start(Module.java:449)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)
    at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)
    at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:419)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1519)

    6) -> It may disappear and then appear again. This is what happened already. When I imported/created new project everything was fine, but then oooopppsss… stopped working.

    Regards,
    Dmitry

    #578876 Reply

    Brian Fernandes
    Moderator

    Dmitry,

    Thanks – looks like you are on the latest version of the product.

    I asked about HTML errors only to ascertain how deep the problem goes – good to know that validation does work.

    org.eclipse.core.internal.resources.ResourceException: The project description file (.project) for ‘qfe’ is missing. This file contains important information about the project. The project will not function properly until this file is restored.

    Is a serious problem – is qfe your Angular project? If the .project file is being deleted or lost, it will significantly affect the support the IDE is able to provide. Can you confirm that the file is present when you start with a new workspace? When you run into the problems, is it absent (you can check the project folder in your OS file explorer).

    Now there’s nothing in the product that will delete this file – can you think of anything else on your system, perhaps something that has also changed recently, that could be deleting this file?

    #578900 Reply

    dmitry-b
    Participant

    I can confirm, that when IDE switched to the new workspace and the project is re-imported from “fresh sources” the problem persists.

    Nothing in the system have been updated or changed that might impact Webclipse behavior.

    Error log is attached.

    Regards,
    Dmitry

    Attachments:
    You must be logged in to view attached files.
    #579254 Reply

    support-tony
    Keymaster

    Dmitry,

    1. Thanks for the log file. Unfortunately, it doesn’t contain anything beyond what might be expected during the launch phase. Do any errors get logged when you are editing some Angular source files from the project? If so, please attach the full log (note that the log is best exported from the error log view to ensure that the full log is available).
    2. In particular, Brian mentioned that the error you highlighted in a previous response suggests that the qfe project may be corrupted (that is, missing a .project file) and it’s not clear that you’ve dealt with that corruption. Sorry, if that is what you meant by “when IDE switched to the new workspace and the project is re-imported from “fresh sources” the problem persists”; we just want to be clear.
    3. If the qfe project is now a valid eclipse project, it may not be recognized as an Angular project. How did you import it from your “fresh sources”?
    4. Can you try creating a new Angular project (in eclipse) and checking whether the validation works with the files generated there? This will tell us if the problem is confined to just specific projects or is affecting all projects.
    5. If the problem is just with specific projects, please send us all the metadata for one of those projects (this is the full project folder but with the source removed – the metadata is in files and folders that start with “.”). This will help us replicate the problem.

    Sorry that you’re continuing to have problems. Whilst it shouldn’t be necessary, one option for you, if possible, is to re-install eclipse and the Angular IDE plug-in at another location to check if that has repaired any corrupted tooling that may have occurred.

    Looking forward to receiving the extra information to help us track this down.

    #579388 Reply

    dmitry-b
    Participant

    1) – Nothing whatsoever. No errors, no highlights.

    2) & 3) – I just re-cloned the project from git repo without any IDE metadata in the sources and then re-imported project from those files i.e. Menu “File-> Open project from file system”.

    4) When the project is created from scratch IDE works, all errors are highlighted correctly.

    5) Workspace and the project “qfe” in it with both workspace metadata and project metadata zip file is attached.

    #579389 Reply

    dmitry-b
    Participant

    zip file attached

    Attachments:
    You must be logged in to view attached files.
    #579444 Reply

    support-tony
    Keymaster

    Dmitry,

    Thanks for the info and the files. We still can’t replicate with the metadata you sent but I did notice that your qfe project is missing a typescript builder and the typescript facet. Although Angular IDE will restore the facet based on the project contents, for some reason, this is not happening with your project. We may need the full project contents (minus the node modules) to figure out why that is. However, a quick solution may be to import the project into a new workspace as an Angular Project, instead of opening as an existing eclipse project. To do this, go to File->Import->Angular->Angular Project, click Next, then browse to the project location, enter the versions of Node and NPM that you want to use, click Finish.

    Please let us know how you get on.

    #579459 Reply

    dmitry-b
    Participant

    I have done what was suggested (“File->Import->Angular->Angular Project”), however the result is still the same.

    Sending source files is not an option.

    It seems that there is no other option but to request refund for the license. I cannot use the product at all.

    Regards,
    Dmitry

    #579478 Reply

    Brian Fernandes
    Moderator

    Dmitry,

    Just to close the loop – this certainly is an odd case that is tied to what looks like (from external analysis) the periodic disappearance of essential metadata from the project.

    If you change your mind about the refund, I would be happy to work through this with you, given that the functionality did work, at one point in time.

    In the meanwhile, I’ll talk to our sales team about a refund.

Viewing 11 posts - 1 through 11 (of 11 total)

The topic ‘IDE stopped highlighting any errors, tips, anything’ is closed to new replies.