October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-724) Create a test for FUSETOOLS-740

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-724?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-724. ------------------------------ Resolution: Out of Date closing as out of date issue > Create a test for FUSETOOLS-740 > ------------------------------- > > Key: JBTIS-724 > URL: https://issues.jboss.org/browse/JBTIS-724 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1175) Update Drools versions to 7.3.0.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1175?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1175. ------------------------------------ pushed to master > Update Drools versions to 7.3.0.Final > ------------------------------------- > > Key: JBTIS-1175 > URL: https://issues.jboss.org/browse/JBTIS-1175 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.5.1.Beta1 > Reporter: Tomas David > Assignee: Tomas David > Fix For: 4.5.1.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25273 at 10/20/17 9:38 AM: -------------------------------------------------------------------- The problem here is not a parsing issue. The tooling displays the correct value and units for the resource that's being edited. It's the resource that's being edited, that's differs: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. for the above to reflect the correct value/unit I would have to edit the deployment config. If I do that things are displayed correctly. [~jeffmaury] thoughts? was (Author: adietish): The problem here is not a parsing issue. The problem here is the resource that's being edited: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. [~jeffmaury] thoughts? > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1175) Update Drools versions to 7.3.0.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1175?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1175: ------------------------------------- Affects Version/s: 4.5.1.Beta1 > Update Drools versions to 7.3.0.Final > ------------------------------------- > > Key: JBTIS-1175 > URL: https://issues.jboss.org/browse/JBTIS-1175 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.5.1.Beta1 > Reporter: Tomas David > Assignee: Tomas David > Fix For: 4.5.1.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1175) Update Drools versions to 7.3.0.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1175?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1175: ------------------------------------- Fix Version/s: 4.5.1.Beta1 > Update Drools versions to 7.3.0.Final > ------------------------------------- > > Key: JBTIS-1175 > URL: https://issues.jboss.org/browse/JBTIS-1175 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.5.1.Beta1 > Reporter: Tomas David > Assignee: Tomas David > Fix For: 4.5.1.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25273 at 10/20/17 9:37 AM: -------------------------------------------------------------------- The problem here is not a parsing issue. The problem here is the resource that's being edited: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. [~jeffmaury] thoughts? was (Author: adietish): The problem here is not a parsing issue. The problem here is the resource that's being edited: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25273: ------------------------------------------ The problem here is not a parsing issue. The problem here is the resource that's being edited: The user operation above edits the *replication controller*. The web-ui does exactly that, it is changing the replication controller. Our tooling is changing the *deployment config*. It only falls back to the replication controller if there's no deployment config. > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25273: ------------------------------------- Comment: was deleted (was: Turns out that the reason for this is in the openshift-restclient-java library. The following json {code} "requests":{ "memory":"5" } {code} is parsed as {code} "requests" => {"memory" => "5Mi"} {code} where it should be *"5"* and not *"5Mi"*.) > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-774) Fuse: Add test for Export Diagram

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-774?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-774. ------------------------------ Resolution: Out of Date closing as out of date issue > Fuse: Add test for Export Diagram > --------------------------------- > > Key: JBTIS-774 > URL: https://issues.jboss.org/browse/JBTIS-774 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Minor > > SSIA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25091) Edit resource limits wizard: Duplicate value "MiB" in Memory Limit & Request

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25091?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25091 at 10/20/17 9:35 AM: -------------------------------------------------------------------- [~jeffmaury] here's the PR for this change: https://github.com/jbosstools/jbosstools-openshift/pull/1598/files was (Author: adietish): [~jeffmaury] here's the PR for this change: https://github.com/jbosstools/jbosstools-openshift/pull/1598/files I discovered a parsing error in the client library that would parse {code} "requests":{ "memory":"5" } {code} as {code} "requests" => {"memory" => "5Mi"} {code} where it should be *"5"* and not *"5Mi"*. I'll filed a separate jira for this: JBIDE-25273 > Edit resource limits wizard: Duplicate value "MiB" in Memory Limit & Request > ---------------------------------------------------------------------------- > > Key: JBIDE-25091 > URL: https://issues.jboss.org/browse/JBIDE-25091 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Josef Kopriva > Priority: Minor > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: edit-resource-limits.png, image-2017-09-22-13-02-35-216.png, request-resource-limit-combo.png, resource-limits-web-console.png > > > When editing memory settings in dialog "Edit resource limits", there is a duplicate value MiB in the Combos for Memory > "Request" and Memory > "Limit": > !edit-resource-limits.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

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 October 2017