[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22603:
------------------------------------------
[~mlabuda] I cannot reproduce this. Do you still experience this (even after JBIDE-21828 was applied)?
Can you please provide steps (matching your env?)
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-20686) Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-20686.
--------------------------------------
Assignee: Andre Dietisheim
Resolution: Rejected
> Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20686
> URL: https://issues.jboss.org/browse/JBIDE-20686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v3, preferences
> Fix For: 4.4.1.S116
>
>
> In OpenShift 3 workbench preference page restoring default setting by clicking on a button Restore Defaults pops up a warning dialog with title "No OpenShift Client binary" and text "Could not find the OpenShift binary "oc" on your path". I would expect that choosing default settings would just clear text field with oc binary location and no dialog is shown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-20686) Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20686:
-------------------------------------
Fix Version/s: 4.4.1.S116
(was: 4.4.x)
> Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20686
> URL: https://issues.jboss.org/browse/JBIDE-20686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, preferences
> Fix For: 4.4.1.S116
>
>
> In OpenShift 3 workbench preference page restoring default setting by clicking on a button Restore Defaults pops up a warning dialog with title "No OpenShift Client binary" and text "Could not find the OpenShift binary "oc" on your path". I would expect that choosing default settings would just clear text field with oc binary location and no dialog is shown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBTIS-791) Fix preview test
by Matej Kralik (JIRA)
Matej Kralik created JBTIS-791:
----------------------------------
Summary: Fix preview test
Key: JBTIS-791
URL: https://issues.jboss.org/browse/JBTIS-791
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, teiid
Affects Versions: 4.3.0.Beta1
Reporter: Matej Kralik
Assignee: Matej Kralik
Priority: Minor
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-132?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan reassigned ERT-132:
--------------------------------
Assignee: Shane Bryzak
> Need to create launch configuration for npm "scripts" [EBZ#491474]
> ------------------------------------------------------------------
>
> Key: ERT-132
> URL: https://issues.jboss.org/browse/ERT-132
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Assignee: Shane Bryzak
> Labels: General, bzira
>
> For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e.
> all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months