March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21815: ------------------------------------------ [~scabanovich] this very much smells like a GTK3, especially you telling that moving your mouse "fixes" it (and then the presence of scrollbars or not). Happy that you found a workaround, even if it's weird, I'd apply it and comment it as workaround in case [~snjeza] doesnt find any better solution. [~snjeza] can you please investigate this (see https://issues.jboss.org/browse/JBIDE-21815?focusedCommentId=13171668&pag... Is this known? > Image metadata not refreshed after name change > ---------------------------------------------- > > Key: JBIDE-21815 > URL: https://issues.jboss.org/browse/JBIDE-21815 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > > Steps to reproduce: > - open the *Deploy Docker Image* wizard > - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}} > - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again. > - ASSERT: the metadata should have been updated > - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3662) CDK Launch config has broken PATH env variable value set

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3662?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3662: ----------------------------------- Regression from JBIDE-21170 > CDK Launch config has broken PATH env variable value set > -------------------------------------------------------- > > Key: JBDS-3662 > URL: https://issues.jboss.org/browse/JBDS-3662 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: path.png > > > Why it duplicates what is already set on installer side? Installer configures everything that is required for vagrant .up to work except SUB_USERNAME and SUB_PASSWORD. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3662) CDK Launch config has broken PATH env variable value set

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3662?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3662: ------------------------------------ Assignee: Rob Stryker (was: Max Rydahl Andersen) > CDK Launch config has broken PATH env variable value set > -------------------------------------------------------- > > Key: JBDS-3662 > URL: https://issues.jboss.org/browse/JBDS-3662 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: path.png > > > Why it duplicates what is already set on installer side? Installer configures everything that is required for vagrant .up to work except SUB_USERNAME and SUB_PASSWORD. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3662) CDK Launch config has broken PATH env variable value set

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3662?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3662: --------------------------------- Fix Version/s: 9.1.0.CR1 > CDK Launch config has broken PATH env variable value set > -------------------------------------------------------- > > Key: JBDS-3662 > URL: https://issues.jboss.org/browse/JBDS-3662 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: path.png > > > Why it duplicates what is already set on installer side? Installer configures everything that is required for vagrant .up to work except SUB_USERNAME and SUB_PASSWORD. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3662) CDK Launch config has broken PATH env variable value set

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3662?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3662: -------------------------------- Attachment: path.png > CDK Launch config has broken PATH env variable value set > -------------------------------------------------------- > > Key: JBDS-3662 > URL: https://issues.jboss.org/browse/JBDS-3662 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: havoc > Attachments: path.png > > > Why it duplicates what is already set on installer side? Installer configures everything that is required for vagrant .up to work except SUB_USERNAME and SUB_PASSWORD. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3662) CDK Launch config has broken PATH env variable value set

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3662?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3662: ----------------------------- > CDK Launch config has broken PATH env variable value set > -------------------------------------------------------- > > Key: JBDS-3662 > URL: https://issues.jboss.org/browse/JBDS-3662 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: havoc > > Why it duplicates what is already set on installer side? Installer configures everything that is required for vagrant .up to work except SUB_USERNAME and SUB_PASSWORD. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3662) CDK Launch config has broken PATH env variable value set

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3662: ----------------------------------- Summary: CDK Launch config has broken PATH env variable value set Key: JBDS-3662 URL: https://issues.jboss.org/browse/JBDS-3662 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: cdk, server Affects Versions: 9.1.0.Beta2 Reporter: Denis Golovin Assignee: Max Rydahl Andersen Priority: Blocker Why it duplicates what is already set on installer side? Installer configures everything that is required for vagrant .up to work except SUB_USERNAME and SUB_PASSWORD. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-21815 at 3/3/16 3:56 PM: ----------------------------------------------------------------------- Well, after trying all kinds of refreshes that were of no use at all, I found one strong remedy, and I know that everyone will be disgusted with it, but it is the only one that works: {code} @Override protected void onPageActivated(DataBindingContext dbc) { if(envViewer != null && envViewer.getControl() != null && !envViewer.getControl().isDisposed()) { Object input = envViewer.getInput(); envViewer.setInput(null); envViewer.setInput(input); } if(dataViewer != null && dataViewer.getControl() != null && !dataViewer.getControl().isDisposed()) { Object input = dataViewer.getInput(); dataViewer.setInput(null); dataViewer.setInput(input); } } {code} I remind that table fails update on its own only when it needs vertical scroll, so it is entirely an UI problem, not model updating and not databinding. was (Author: scabanovich): Well, after trying all kinds of refreshes that were of no use at all, I found one strong remedy, and I know that everyone will be disgusted with it, but it is the only one that works: {code} @Override protected void onPageActivated(DataBindingContext dbc) { if(envViewer != null && envViewer.getControl() != null && !envViewer.getControl().isDisposed()) { Object input = envViewer.getInput(); envViewer.setInput(null); envViewer.setInput(input); } if(dataViewer != null && dataViewer.getControl() != null && !dataViewer.getControl().isDisposed()) { Object input = dataViewer.getInput(); dataViewer.setInput(null); dataViewer.setInput(input); } } {code} I remind that table fails update on its own only when it needs vertical scroll, so it is entirely an UI problem, not model update. > Image metadata not refreshed after name change > ---------------------------------------------- > > Key: JBIDE-21815 > URL: https://issues.jboss.org/browse/JBIDE-21815 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > > Steps to reproduce: > - open the *Deploy Docker Image* wizard > - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}} > - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again. > - ASSERT: the metadata should have been updated > - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21815: ----------------------------------------------- Well, after trying all kinds of refreshes that were of no use at all, I found one strong remedy, and I know that everyone will be disgusted with it, but it is the only one that works: {code} @Override protected void onPageActivated(DataBindingContext dbc) { if(envViewer != null && envViewer.getControl() != null && !envViewer.getControl().isDisposed()) { Object input = envViewer.getInput(); envViewer.setInput(null); envViewer.setInput(input); } if(dataViewer != null && dataViewer.getControl() != null && !dataViewer.getControl().isDisposed()) { Object input = dataViewer.getInput(); dataViewer.setInput(null); dataViewer.setInput(input); } } {code} I remind that table fails update on its own only when it needs vertical scroll, so it is entirely an UI problem, not model update. > Image metadata not refreshed after name change > ---------------------------------------------- > > Key: JBIDE-21815 > URL: https://issues.jboss.org/browse/JBIDE-21815 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > > Steps to reproduce: > - open the *Deploy Docker Image* wizard > - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}} > - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again. > - ASSERT: the metadata should have been updated > - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-21815 at 3/3/16 2:54 PM: ----------------------------------------------------------------------- [~xcoulon], [~jcantrill], I finally reproduced it with the mock model, and it is very strange use case. So, even if there may be a problem with docker model, there is one in UI too. When I make wizard high enough for 'Environment variables:' and 'Data volumes:' tables to show all entries without scroll, they are updated perfectly. When I make height of wizard so low, that table(s) need scroll, it is not updated until I just pass mouse over it (a magician pass, indeed). I checked that all requests getEnvironmentVariables() and getVolumes() are made before I switch to the second page, that means that during the mouse pass table only updates labels, it already has correct data, but is too lazy too refresh items. was (Author: scabanovich): [~xcoulon], [~jcantrill], I finally reproduced it with the mock model, and it is very strange use case. So, even if there may be a problem with docker model, there is one in UI too. When I make wizard high enough for 'Environment variables:' and 'Data volumes:' tables to show all entries without scroll, they are updated perfectly. When I make height of wizard so low, that table 'Data volumes:' needs scroll, it is not updated until I just pass mouse over it (a magician pass, indeed). That does not happen to table 'Environment variables:' which never has scrolling (is not it a bug by itself, user will not be able to see all variables if they are too many?) I checked that all requests getVolumes() are made before I switch to the second page, that means that during the mouse pass table only updates labels, it already has correct data, but is too lazy too refresh items. > Image metadata not refreshed after name change > ---------------------------------------------- > > Key: JBIDE-21815 > URL: https://issues.jboss.org/browse/JBIDE-21815 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > > Steps to reproduce: > - open the *Deploy Docker Image* wizard > - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}} > - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again. > - ASSERT: the metadata should have been updated > - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016