[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21828 at 3/9/16 5:27 AM:
------------------------------------------------------------------
[~scabanovich] I partly agree on your 1st comment that initially events should not be fired: look at how most observable frameworks work: they always fire, they wont differ if it's a 1st call or a subsequent one. The firing though wont be executed on a more general condition (not based on the fact if this is the first or 2nd, 3rd, etc. call): the firing wont happen if there's no change in the values (see for instance the firing code in PropertyChangeSupport which does not execute the firing if there's no change btw. oldValue and newValue).
was (Author: adietish):
[~scabanovich] I partly agree on your 1st comment that initially events should not be fired: look at how most observable frameworks work: they always fire, they wont differ if it's a 1st call or a subsequent one. The firing though wont be executed on a more general condition: the firing wont happen if there's no change in the values (see for instance the firing code in PropertyChangeSupport which does not execute the firing if there's no change btw. oldValue and newValue).
> OpenShift Explorer view flickers when refreshing a service
> ----------------------------------------------------------
>
> Key: JBIDE-21828
> URL: https://issues.jboss.org/browse/JBIDE-21828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Attachments: Screenshot 2016-03-08 10.32.39.png
>
>
> When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
> Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod.
> Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
> Custom/added logs in the console:
> {code}
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21828:
------------------------------------------
[~scabanovich] I partly agree on your 1st comment that initially events should not be fired: look at how most observable frameworks work: they always fire, they wont differ if it's a 1st call or a subsequent one. The firing though wont be executed on a more general condition: the firing wont happen if there's no change in the values (see for instance the firing code in PropertyChangeSupport which does not execute the firing if there's no change btw. oldValue and newValue).
> OpenShift Explorer view flickers when refreshing a service
> ----------------------------------------------------------
>
> Key: JBIDE-21828
> URL: https://issues.jboss.org/browse/JBIDE-21828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Attachments: Screenshot 2016-03-08 10.32.39.png
>
>
> When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
> Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod.
> Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
> Custom/added logs in the console:
> {code}
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21725?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21725:
---------------------------------------
https://github.com/jbosstools/jbosstools-build/pull/213 is merged. Now this PR removes the properties from integration tests:
https://github.com/jbosstools/jbosstools-integration-tests/pull/1456
> Use RedDeer 1.x nightly in master builds
> ----------------------------------------
>
> Key: JBIDE-21725
> URL: https://issues.jboss.org/browse/JBIDE-21725
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> Martin said:
> {quote}Nick Boldt, ok, I will discuss this with others and then get back to you - I'm not sure if now is the right time to pull a nightly or we should wait.
> I think the intention was to have this in the TP so that we know exactly what is used with which version of JBT - just look in the corresponding TP. That's also how it works for server depending on base - it's the same version. But pointing to RedDeer master repo is different.
> After discussion with Rastislav Wagner, here's our proposal: What if we stick with RedDeer master repo in our pom for integration tests master? For maintenance branch (4.3.x), it's good that we have a stable version of RedDeer in the TP and we can use that. But for JBT master, we can rely on the RedDeer master repo directly and later when we start testing JBT 4.4.0.Alpha1, we may put some version of RedDeer to the TP and switch to that.
> What do you think? Makes sense?
> So if you agree, this would mean that for now we won't use RedDeer in TP 4.60.0 - so either you can just leave it there until we replace it with a new version, or you could even remove it.{quote}
> Nick said:
> {quote}Makes sense. When stable, add to TP; until stable, just use nightly.
> Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1].
> [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
> Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL.{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21725?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-21725:
----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/213, https://github.com/jbosstools/jbosstools-integration-tests/pull/1456 (was: https://github.com/jbosstools/jbosstools-build/pull/213)
> Use RedDeer 1.x nightly in master builds
> ----------------------------------------
>
> Key: JBIDE-21725
> URL: https://issues.jboss.org/browse/JBIDE-21725
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> Martin said:
> {quote}Nick Boldt, ok, I will discuss this with others and then get back to you - I'm not sure if now is the right time to pull a nightly or we should wait.
> I think the intention was to have this in the TP so that we know exactly what is used with which version of JBT - just look in the corresponding TP. That's also how it works for server depending on base - it's the same version. But pointing to RedDeer master repo is different.
> After discussion with Rastislav Wagner, here's our proposal: What if we stick with RedDeer master repo in our pom for integration tests master? For maintenance branch (4.3.x), it's good that we have a stable version of RedDeer in the TP and we can use that. But for JBT master, we can rely on the RedDeer master repo directly and later when we start testing JBT 4.4.0.Alpha1, we may put some version of RedDeer to the TP and switch to that.
> What do you think? Makes sense?
> So if you agree, this would mean that for now we won't use RedDeer in TP 4.60.0 - so either you can just leave it there until we replace it with a new version, or you could even remove it.{quote}
> Nick said:
> {quote}Makes sense. When stable, add to TP; until stable, just use nightly.
> Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1].
> [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
> Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL.{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21840) Checkbox to save password in Secure Storage is not checked when password is stored
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21840:
-------------------------------------
Summary: Checkbox to save password in Secure Storage is not checked when password is stored
Key: JBIDE-21840
URL: https://issues.jboss.org/browse/JBIDE-21840
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
In OpenShift connection wizard there is a checkbox to store password/token in secure storage. If I choose on an existing OpenShift 3 connection with basic authentication to store password in secure storage, technically it is stored and visible on Secure Storage preference page, but in Connection wizard it is not visible. Upon next opening of the Edit Connection wizard, checkbox is unchecked although password is checked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21840) Checkbox to save password in Secure Storage is not checked when password is stored
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21840?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21840:
----------------------------------
Labels: openshift_v3 (was: )
> Checkbox to save password in Secure Storage is not checked when password is stored
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-21840
> URL: https://issues.jboss.org/browse/JBIDE-21840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3
>
> In OpenShift connection wizard there is a checkbox to store password/token in secure storage. If I choose on an existing OpenShift 3 connection with basic authentication to store password in secure storage, technically it is stored and visible on Secure Storage preference page, but in Connection wizard it is not visible. Upon next opening of the Edit Connection wizard, checkbox is unchecked although password is checked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21839) Cannot connect to Karaf via JMX
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBIDE-21839:
------------------------------------
Summary: Cannot connect to Karaf via JMX
Key: JBIDE-21839
URL: https://issues.jboss.org/browse/JBIDE-21839
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.3.1.Beta2
Environment: JBDS 9.1.0.Beta2
Reporter: Tomáš Sedmík
Attachments: out.ogv
I'm unable to connect to Apache Karaf runtime via JMX Navigator --> Local Processes (see attached video)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month