[JBoss JIRA] (JBIDE-26073) Manage Projects Wizard: Dialog-text to confirm removal says "<missing argument">
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26073?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26073:
-------------------------------------
Description:
# ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
# ASSERT: have at least 1 project in your OpenShift
# EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
# ASSERT: "Manage Projects" wizard shows up, listing all projects
# EXEC: select 1 project and hit "Remove..."
Result:
A dialog shows up asking you to confirm the removal. The message shows "<missing argument>"
!dialog-missing-argument.png!
was:
# ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
# ASSERT: have at least 1 project in your OpenShift
# EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
# ASSERT: "Manage Projects" wizard shows up, listing all projects
# EXEC: select 1 project and hit "Remove..."
Result:
A dialog shows up asking you to confirm the removal. The message shows "<missing argument>"
> Manage Projects Wizard: Dialog-text to confirm removal says "<missing argument">
> --------------------------------------------------------------------------------
>
> Key: JBIDE-26073
> URL: https://issues.jboss.org/browse/JBIDE-26073
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.6.x
>
> Attachments: dialog-missing-argument.png
>
>
> # ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
> # ASSERT: have at least 1 project in your OpenShift
> # EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
> # ASSERT: "Manage Projects" wizard shows up, listing all projects
> # EXEC: select 1 project and hit "Remove..."
> Result:
> A dialog shows up asking you to confirm the removal. The message shows "<missing argument>"
> !dialog-missing-argument.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26072) Manage Projects wizard: project that I deleted is still listed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26072?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26072:
------------------------------------------
This again is a usecase where terminating projects, that are in the process of being deleted, cause weirdness.
I think that terminating projects should be listed, but we should inform the user about the fact that the project is being deleted.
Ideally we'd display a state column for the projects and watch events, updating the list when the project finally disappears.
> Manage Projects wizard: project that I deleted is still listed
> --------------------------------------------------------------
>
> Key: JBIDE-26072
> URL: https://issues.jboss.org/browse/JBIDE-26072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Attachments: image-2018-06-01-16-08-59-257.png
>
>
> steps:
> # ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
> # ASSERT: have at least 1 project in your OpenShift
> # EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
> # ASSERT: "Manage Projects" wizard shows up, listing all projects
> # EXEC: select 1 project and hit "Remove..."
> # EXEC: when asked to confirm the removal, hit "OK"
> # ASSERT: wizard gets disabled, progress bar shows up telling you that your project is being deleted.
> Result:
> Once the progressbar is gone and all the wizard is enabled again, the project is still listed
> !image-2018-06-01-16-08-59-257.png!
> Workaround: hit "Refresh..."
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26072) Manage Projects wizard: project that I deleted is still listed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26072?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26072:
-------------------------------------
Description:
steps:
# ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
# ASSERT: have at least 1 project in your OpenShift
# EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
# ASSERT: "Manage Projects" wizard shows up, listing all projects
# EXEC: select 1 project and hit "Remove..."
# EXEC: when asked to confirm the removal, hit "OK"
# ASSERT: wizard gets disabled, progress bar shows up telling you that your project is being deleted.
Result:
Once the progressbar is gone and all the wizard is enabled again, the project is still listed
!image-2018-06-01-16-08-59-257.png!
Workaround: hit "Refresh..."
was:
steps:
# ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
# ASSERT: have at least 1 project in your OpenShift
# EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
# ASSERT: "Manage Projects" wizard shows up, listing all projects
# EXEC: select 1 project and hit "Remove..."
# EXEC: when asked to confirm the removal, hit "OK"
# ASSERT: wizard gets disabled, progress bar shows up telling you that your project is being deleted.
Result:
Once the progressbar is gone and all the wizard is enabled again, the project is still listed
!image-2018-06-01-16-08-59-257.png!
Workaround: hit "Refresh"
> Manage Projects wizard: project that I deleted is still listed
> --------------------------------------------------------------
>
> Key: JBIDE-26072
> URL: https://issues.jboss.org/browse/JBIDE-26072
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Attachments: image-2018-06-01-16-08-59-257.png
>
>
> steps:
> # ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
> # ASSERT: have at least 1 project in your OpenShift
> # EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
> # ASSERT: "Manage Projects" wizard shows up, listing all projects
> # EXEC: select 1 project and hit "Remove..."
> # EXEC: when asked to confirm the removal, hit "OK"
> # ASSERT: wizard gets disabled, progress bar shows up telling you that your project is being deleted.
> Result:
> Once the progressbar is gone and all the wizard is enabled again, the project is still listed
> !image-2018-06-01-16-08-59-257.png!
> Workaround: hit "Refresh..."
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26072) Manage Projects wizard: project that I deleted is still listed
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26072:
----------------------------------------
Summary: Manage Projects wizard: project that I deleted is still listed
Key: JBIDE-26072
URL: https://issues.jboss.org/browse/JBIDE-26072
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.6.0.AM2
Reporter: Andre Dietisheim
Attachments: image-2018-06-01-16-08-59-257.png
steps:
# ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
# ASSERT: have at least 1 project in your OpenShift
# EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
# ASSERT: "Manage Projects" wizard shows up, listing all projects
# EXEC: select 1 project and hit "Remove..."
# EXEC: when asked to confirm the removal, hit "OK"
# ASSERT: wizard gets disabled, progress bar shows up telling you that your project is being deleted.
Result:
Once the progressbar is gone and all the wizard is enabled again, the project is still listed
!image-2018-06-01-16-08-59-257.png!
Workaround: hit "Refresh"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25916) OpenShift Server Adapter: Error in Log after "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25916?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25916:
------------------------------------------
Even halting at breakpoints when debugging works. But stepping around in the code is not usable, it's very slow, a real pain.
> OpenShift Server Adapter: Error in Log after "Restart in Debug"
> ---------------------------------------------------------------
>
> Key: JBIDE-25916
> URL: https://issues.jboss.org/browse/JBIDE-25916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.Final
> Environment: F28 + Red Hat JBoss Developer Studio Build id: GA-v20180410-1152-B2341
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: debugging, server_adapter
> Fix For: 4.6.0.AM3
>
> Attachments: error-launching-server.png
>
>
> An error occurs when restarting server adapter in debug:
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Warning
> Wed Apr 11 18:09:03 CEST 2018
> Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> org.eclipse.core.runtime.CoreException: Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.handleSyncDownFailure(OpenShiftPublishController.java:92)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:61)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182)
> at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1340)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$1.run(OpenShiftLaunchController.java:261)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Contains: Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war
> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3]
> error: exit status 23
> {code}
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Apr 11 18:09:03 CEST 2018
> Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> {code}
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Apr 11 18:09:03 CEST 2018
> Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war
> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3]
> error: exit status 23
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25916) OpenShift Server Adapter: Error in Log after "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25916?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25916:
------------------------------------------
I cannot reproduce this any more. I dont have any errors either. [~jkopriva] can you?
> OpenShift Server Adapter: Error in Log after "Restart in Debug"
> ---------------------------------------------------------------
>
> Key: JBIDE-25916
> URL: https://issues.jboss.org/browse/JBIDE-25916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.Final
> Environment: F28 + Red Hat JBoss Developer Studio Build id: GA-v20180410-1152-B2341
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: debugging, server_adapter
> Fix For: 4.6.0.AM3
>
> Attachments: error-launching-server.png
>
>
> An error occurs when restarting server adapter in debug:
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Warning
> Wed Apr 11 18:09:03 CEST 2018
> Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> org.eclipse.core.runtime.CoreException: Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.handleSyncDownFailure(OpenShiftPublishController.java:92)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:61)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182)
> at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1340)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$1.run(OpenShiftLaunchController.java:261)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Contains: Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war
> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3]
> error: exit status 23
> {code}
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Apr 11 18:09:03 CEST 2018
> Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> {code}
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Apr 11 18:09:03 CEST 2018
> Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war
> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3]
> error: exit status 23
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
