August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 8/30/17 8:44 AM: ------------------------------------------------------------------- * Router timeout: according to the [docs|https://docs.openshift.org/latest/install_config/configuring_routing...] one can override the global timeout for a specific route by annotating it: {code} { ... "kind": "Route", "metadata": { "annotations": { "haproxy.router.openshift.io/timeout": "1h", {code} Using oc one has to do {code} # oc annotate route myroute --overwrite haproxy.router.openshift.io/timeout=2s {code} As a non-admin user I can process this change and it seems effective. This is a change that we could apply to the route when debugging, removing it once we stop the debugging. * Debug connection timeout: Doing a keepalive-ping within the debug connection as arquilian does seems not to be possible for us since we're not in control of the sockets that are used for this sake. * lifenessprobe: this seems like an edge case, not critical. I ack though that with a lifeness probe in place debugging gets annoying since the user would have to manually remove it before and add it back in after debugging. [~jeffmaury], [~rhuss], [~aurelien.pupier] Thoughts? was (Author: adietish): according to the [docs|https://docs.openshift.org/latest/install_config/configuring_routing...] one can override the global timeout for a specific route by annotating it: {code} { ... "kind": "Route", "metadata": { "annotations": { "haproxy.router.openshift.io/timeout": "1h", {code} Using oc one has to do {code} # oc annotate route myroute --overwrite haproxy.router.openshift.io/timeout=2s {code} As a non-admin user I can process this change and it seems effective. This is a change that we could apply to the route when debugging, removing it once we stop the debugging. [~jeffmaury], [~rhuss], [~aurelien.pupier] Thoughts? > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24293) Lot of blank lines written to terminal when starting the CDK server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24293?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24293: ------------------------------------ Yes it is related to HyperV. The output uses a lot of escapes, I even saw some part of my terminal being updated at the top of the window and blue colored !!! Will make a small video. Maybe reverting to using Eclipse terminal instead of console will be better ? > Lot of blank lines written to terminal when starting the CDK server > ------------------------------------------------------------------- > > Key: JBIDE-24293 > URL: https://issues.jboss.org/browse/JBIDE-24293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.x > > Attachments: terminalOutputWhenStartingCDK.txt > > > Windows 10 > Version: 10.4.0.AM3 > Build id: AM3-v20170406-1058-B390 > Build date: 20170406-1058 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24868: ------------------------------------------ according to the [docs|https://docs.openshift.org/latest/install_config/configuring_routing...] one can override the global timeout for a specific route by annotating it: {code} { ... "kind": "Route", "metadata": { "annotations": { "haproxy.router.openshift.io/timeout": "1h", {code} Using oc one has to do {code} # oc annotate route myroute --overwrite haproxy.router.openshift.io/timeout=2s {code} As a non-admin user I can process this change and it seems effective. This is a change that we could apply to the route when debugging, removing it once we stop the debugging. [~jeffmaury], [~rhuss], [~aurelien.pupier] Thoughts? > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4482) Create 'About' dialog to show most relevant information about installer

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-4482?page=com.atlassian.jira.plugin.... ] Mohit Suman updated JBDS-4482: ------------------------------ Sprint: devex #137 September 2017 > Create 'About' dialog to show most relevant information about installer > ----------------------------------------------------------------------- > > Key: JBDS-4482 > URL: https://issues.jboss.org/browse/JBDS-4482 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 11.0.0.GA > Reporter: Denis Golovin > Assignee: Sudhir Verma > Labels: New_and_noteworthy, ui > Fix For: 11.x > > > Dialog should contain: > 1. Application logo, name and version > 2. Link to documentation > 3. Link to release notes > 4. Link to documentation how to report issues > Dialog can be requested trough context menu 'About' and should show modal dialog with content listed above > Good Example is Atom editor About Page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4523) Tests for installing all available items

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4523?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4523: ------------------------------ Sprint: devex #137 September 2017 > Tests for installing all available items > ---------------------------------------- > > Key: JBDS-4523 > URL: https://issues.jboss.org/browse/JBDS-4523 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 11.1.0.AM2 > > > Extend the current default install tests to be able to select additional (all) components. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4524) Automated checks for installed components

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4524?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4524: ------------------------------ Sprint: devex #137 September 2017 > Automated checks for installed components > ----------------------------------------- > > Key: JBDS-4524 > URL: https://issues.jboss.org/browse/JBDS-4524 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 11.1.0.AM2 > > > Create tests that check the (default) installed products. > Possible checks include: > - version > - user configuration > - registry entry -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4521) Create automated tests for test cases that can be automated

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4521?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4521: ------------------------------ Sprint: devex #137 September 2017 > Create automated tests for test cases that can be automated > ----------------------------------------------------------- > > Key: JBDS-4521 > URL: https://issues.jboss.org/browse/JBDS-4521 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 11.1.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4522) Add tests/infrastructure for testing with 'abnormal' windows user names

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4522?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4522: ------------------------------ Sprint: devex #137 September 2017 > Add tests/infrastructure for testing with 'abnormal' windows user names > ----------------------------------------------------------------------- > > Key: JBDS-4522 > URL: https://issues.jboss.org/browse/JBDS-4522 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Environment: windows > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 11.1.0.AM2 > > > Need automated tests for windows users with spaces/non-ascii characters in their name (both seem to be actually quite often used) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24797: ------------------------------------------ * The most practical solution that I see is to find a checkstyle config that matches the default Eclipse formatter. * Eclipse [Checkstyle plugin can create an Eclipse formatter|https://stackoverflow.com/a/9665882/231357] that's based on Checkstyle rules. IMHO this is doable but annoying given that it requires people to set the checkstyle based formatter. * Apache CXF is using [automated scripts|https://cxf.apache.org/connecting-maven-eclipse-checkstyle-and-pm...] that generate and install Eclipse formatters + checkstyle rules based on configurations > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.1.AM2 > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24681) ITests: Get rid of AbstractCreateApplicationTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24681?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-24681: --------------------------------------- The rest will be part of https://issues.jboss.org/browse/JBIDE-23131 > ITests: Get rid of AbstractCreateApplicationTest > ------------------------------------------------ > > Key: JBIDE-24681 > URL: https://issues.jboss.org/browse/JBIDE-24681 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Josef Kopriva > Fix For: 4.5.1.AM2 > > > Use requirements instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 August 2017