[JBoss JIRA] (JBIDE-25677) Server adapter: Timers are incorrectly managed
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25677?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-25677:
----------------------------------
Assignee: Andre Dietisheim
> Server adapter: Timers are incorrectly managed
> ----------------------------------------------
>
> Key: JBIDE-25677
> URL: https://issues.jboss.org/browse/JBIDE-25677
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.x
>
>
> Timers are incorrectly managed in OpenShift server adapter. I tried to create a NodeJS server adapter on OpenShift Online Starter. As the first rsync is long (thanks to .npm and node_modules), it may take more than 5mns as OpenShift Online Starter is resource limited. I think we should rather monitor the activity of the rsync operation (through messages) and set a timer related to this activity.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25547) Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25547?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25547:
------------------------------------
[~rob.stryker] can you verify this one because I think this is fixed
> Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25547
> URL: https://issues.jboss.org/browse/JBIDE-25547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: connection-wizard.png
>
>
> # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location
> # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid
> (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc)
> # EXEC: launch connection wizard
> # EXEC: provide server url and authentication means
> # ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area
> !connection-wizard.png!
> Result:
> You cannot save your connection unless you override the oc location for this connection. In order to correct the preferences you have to cancel the wizard and go to the preferences. Once you correct the value in preferences, you are not prevented from saving the connection any more.
> Expected result:
> Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25644) Delete Resources: Scrollbars are not visible, scrolling stops working after resize
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25644?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25644:
-------------------------------
Fix Version/s: 4.5.3.AM2
(was: 4.5.x)
> Delete Resources: Scrollbars are not visible, scrolling stops working after resize
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25644
> URL: https://issues.jboss.org/browse/JBIDE-25644
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + DevStudio 11.2.0.GA, Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: delete_resources
> Fix For: 4.5.3.AM2
>
> Attachments: image-2018-01-24-15-34-06-459.png, image-2018-01-24-15-34-31-837.png, image-2018-01-24-15-35-04-125.png
>
>
> I have found several UI errors in this dialog:
> - Scrolling bars not visible on Fedora (I have not tested it on other OS yet)
> - After resize scrolling stops working
> - When I enter simple label (e.g. camel), results after deleting label are different:
> Before entering:
> !image-2018-01-24-15-34-06-459.png|thumbnail!
> With label:
> !image-2018-01-24-15-34-31-837.png|thumbnail!
> After deleting label:
> !image-2018-01-24-15-35-04-125.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25644) Delete Resources: Scrollbars are not visible, scrolling stops working after resize
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25644?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25644:
-------------------------------
Sprint: devex #145 February 2018
> Delete Resources: Scrollbars are not visible, scrolling stops working after resize
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25644
> URL: https://issues.jboss.org/browse/JBIDE-25644
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + DevStudio 11.2.0.GA, Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: delete_resources
> Fix For: 4.5.3.AM2
>
> Attachments: image-2018-01-24-15-34-06-459.png, image-2018-01-24-15-34-31-837.png, image-2018-01-24-15-35-04-125.png
>
>
> I have found several UI errors in this dialog:
> - Scrolling bars not visible on Fedora (I have not tested it on other OS yet)
> - After resize scrolling stops working
> - When I enter simple label (e.g. camel), results after deleting label are different:
> Before entering:
> !image-2018-01-24-15-34-06-459.png|thumbnail!
> With label:
> !image-2018-01-24-15-34-31-837.png|thumbnail!
> After deleting label:
> !image-2018-01-24-15-35-04-125.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years