[JBoss JIRA] (JBIDE-22894) ResourceException below IDETernProject.getTernProject (thrown in Project.checkAccessible)
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22894?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-22894:
--------------------------------
Sprint: devex #124 December 2017 (was: devex #123 November 2016)
> ResourceException below IDETernProject.getTernProject (thrown in Project.checkAccessible)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22894
> URL: https://issues.jboss.org/browse/JBIDE-22894
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Victor Rubezhny
> Fix For: 4.4.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Error while tern file synchronization
> {noformat}
> org.eclipse.core.internal.resources.ResourceException: Resource '/reporting-app' is not open.
> at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:143)
> at org.eclipse.core.internal.resources.Resource.checkAccessibleAndLocal(Resource.java:214)
> at org.eclipse.core.internal.resources.Resource.getSessionProperty(Resource.java:1206)
> at tern.eclipse.ide.internal.core.resources.IDETernProject.getTernProject(IDETernProject.java:708)
> at tern.eclipse.ide.internal.core.resources.IDETernProjectSynchronizer.disposeTernProject(IDETernProjectSynchronizer.java:93)
> at tern.eclipse.ide.internal.core.resources.IDETernProjectSynchronizer.resourceChanged(IDETernProjectSynchronizer.java:69)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
> at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:265)
> at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:368)
> at org.eclipse.core.internal.resources.Resource.broadcastPreDeleteEvent(Resource.java:1884)
> at org.eclipse.core.internal.resources.Resource.delete(Resource.java:766)
> at org.eclipse.core.internal.resources.Project.delete(Project.java:323)
> at org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:160)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306)
> at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {noformat}
> The reporter(s) left the following comment(s):
> --- Anonymous wrote on [1935|https://redhat.ctrlflow.com/reviewers/#!/incidents/57a208eee4b0fe642...]: ---
> To reporoduce:
> 1. delete project file from fs: .project
> 2. delete project from eclipse without removing fs
> --- Chris Stone wrote on [ba6d|https://redhat.ctrlflow.com/reviewers/#!/incidents/5769adebe4b024630...]: ---
> Deleting a closed project, including files on disk.
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.10.0.v20150423-0755 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160606-1342 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.ltk.core.refactoring | 3.6.200.v20140826-0859 | 3.7.0.v20160419-0705 |
> | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.8.0.v20160518-1817 |
> | org.eclipse.rse.files.ui | 3.2.200.201502052140 | 3.2.200.201507172213 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.navigator.resources | 3.5.1.v20160128-1644 | 3.5.100.v20160518-1929 |
> | org.eclipse.ui.views | 3.8.0.v20150422-0725 | 3.8.0.v20150422-0725 |
> | tern.eclipse.ide.core | 1.1.0.201511082254 | 1.2.0.201606211556 |
> Operating Systems:
> | Linux | 2.6.32.1 | 4.6.4.fc24 |
> | MacOSX | 10.10.5 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5762a96fe4b075777d...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-22362:
--------------------------------
Sprint: devex #119 August 2016, devex #120 September 2016 (was: devex #119 August 2016, devex #120 September 2016, devex #123 November 2016)
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.AM1
>
> Attachments: enabling-dev-mode-has-encountered-an-error.png
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-23422:
--------------------------------
Sprint: (was: devex #123 November 2016)
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.3.AM1
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months