August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24899: ---------------------------------- Description: Exception in Error log: {code:java} Failed to inspect image: '172.30.1.1:5000/test/hola:latest' com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404 at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084) at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023) at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326) ... 5 more Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008) at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816) at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92) at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773) at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198) at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79) at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340) at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) eclipse.buildId=11.1.0.AM1-v20170824-1835-B873 java.version=1.8.0_141 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product com.jboss.devstudio.core.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product {code} > Deploy Docker Image wizard: Image not found > ------------------------------------------- > > Key: JBIDE-24899 > URL: https://issues.jboss.org/browse/JBIDE-24899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Attachments: image-2017-08-29-09-50-20-927.png > > > Exception in Error log: > {code:java} > Failed to inspect image: '172.30.1.1:5000/test/hola:latest' > com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404 > at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084) > at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023) > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326) > ... 5 more > Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found > at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008) > at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816) > at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92) > at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773) > at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198) > at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79) > at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) > at org.glassfish.jersey.internal.Errors.process(Errors.java:315) > at org.glassfish.jersey.internal.Errors.process(Errors.java:297) > at org.glassfish.jersey.internal.Errors.process(Errors.java:267) > at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340) > at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > eclipse.buildId=11.1.0.AM1-v20170824-1835-B873 > java.version=1.8.0_141 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24899: ---------------------------------- Steps to Reproduce: >From https://issues.jboss.org/browse/JBIDE-24501 : ASSERT: have the CDK with the registry that's not publicly reachable ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git) ASSERT: have a connection to the docker daemon in the CDK3 EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick Docker Connection to the docker daemon in the CDK EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..." EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..." ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix EXEC: select different project EXEC: select "Push Image to registry" EXEC: hit "Next" ASSERT: Error dialog shows up: "No Docker image named 172.30.1.1:5000/test/hola:latest could be found" !image-2017-08-29-09-50-20-927.png|thumbnail! Screencast: https://youtu.be/JolnbsW1lTw was: >From https://issues.jboss.org/browse/JBIDE-24501 : ASSERT: have the CDK with the registry that's not publicly reachable ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git) ASSERT: have a connection to the docker daemon in the CDK3 EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick Docker Connection to the docker daemon in the CDK EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..." EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..." ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix EXEC: select different project EXEC: select "Push Image to registry" EXEC: hit "Next" ASSERT: Error dialog shows up: "No Docker image named 172.30.1.1:5000/test/hola:latest could be found" !image-2017-08-29-09-50-20-927.png|thumbnail! > Deploy Docker Image wizard: Image not found > ------------------------------------------- > > Key: JBIDE-24899 > URL: https://issues.jboss.org/browse/JBIDE-24899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Attachments: image-2017-08-29-09-50-20-927.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-24899: ------------------------------------- Summary: Deploy Docker Image wizard: Image not found Key: JBIDE-24899 URL: https://issues.jboss.org/browse/JBIDE-24899 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk, docker, openshift Affects Versions: 4.5.1.AM1 Reporter: Josef Kopriva Attachments: image-2017-08-29-09-50-20-927.png -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4512) Create test of rh-eclipse47 label

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4512?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4512: ------------------------------- Summary: Create test of rh-eclipse47 label (was: Create test for rh-eclipse47) > Create test of rh-eclipse47 label > --------------------------------- > > Key: JBDS-4512 > URL: https://issues.jboss.org/browse/JBDS-4512 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: integration-tests > Affects Versions: 11.1.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 11.1.0.AM2 > > > We need to test if slave is properly configured for testing/building if Devstudio RPM. We have to test results of work of rh-eclipse47.sh, rh-eclipse47-devstudio-snapshots-11-repo.sh, sudoers (see \[1\]). > \[1\] https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/t... > Tests should to be stored at \[2\]. > \[2\] https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-env-suite/tree... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24896) Cannot start any JBoss server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24896?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24896. --------------------------------- It seems all is good now. Tested a few servers in devstudio-11.1.0.AM2-v20170828-2243-B917-installer-standalone.jar . > Cannot start any JBoss server > ----------------------------- > > Key: JBIDE-24896 > URL: https://issues.jboss.org/browse/JBIDE-24896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.1.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.1.AM2 > > > When I try to start any server such as WildFly or EAP 6/7, I immediately get a NPE: > {code} > An internal error occurred during: "Starting WildFly 10.1". > java.lang.NullPointerException > {code} > {code} > An internal error occurred during: "Starting WildFly 10.1". > java.lang.NullPointerException > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XMLDocumentRepository.refresh(XMLDocumentRepository.java:131) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:146) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:84) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:132) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:114) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:218) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:204) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:67) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:126) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:110) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} > I tried EAP 6.4, 7.0, 7.1 and WildFly 10.1. > This is with devstudio 11.1.0.AM1 B873. > As indicated by Rob, this is likely caused by this commit from JBIDE-24758: > https://github.com/jbosstools/jbosstools-server/commit/1a58a4d54097e4d927... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24501: ------------------------------------ [~jkopriva] Tested with DevStudio 11.0.0.GA. It"s ok for me as the purpose of this fix is to get rid of the first error dialog (An internal error occurred). > Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24501 > URL: https://issues.jboss.org/browse/JBIDE-24501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM (headless)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23882: --------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.x) > Automate test of installation of software from Red Hat Central into devstudio RPM (headless) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24448) Application wizard: error decoration is not removed when I correct "Custom Template" url to be valid

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24448?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-24448. --------------------------------- Closing, decorator is ok. Verified in: Version: 11.1.0.AM1 Build id: AM1-v20170824-1835-B873 Build date: 20170824-1835 & Win10 > Application wizard: error decoration is not removed when I correct "Custom Template" url to be valid > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-24448 > URL: https://issues.jboss.org/browse/JBIDE-24448 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Environment: Win 10. > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.5.1.AM1 > > > Error decorator is not redrawn until windows is resized. > See screencast: https://youtu.be/BQo-NtDS_c0 > For more detailed info, see JBIDE-23473 > I tried it on Win10 & Fedora 25.... Win10 has this issue, Fedora 25 does not. > Mac is not affected either. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24586) Stabilize CDI and EasyImport tests

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24586?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24586: --------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM2) > Stabilize CDI and EasyImport tests > ---------------------------------- > > Key: JBIDE-24586 > URL: https://issues.jboss.org/browse/JBIDE-24586 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: install-tests, qa > Affects Versions: 4.5.0.AM2 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.x > > > CDI, Deltaspike and Easy import tests are randomly failing on Oxygen (more then on Neon). Need to find out why and fix it. > Especially on Mac all tests are failing because RedDeer isn't able to fullfill requirements (probably). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22810. --------------------------------- Closing. I was not able to reproduce it in devstudio: Version: 11.1.0.AM1 Build id: AM1-v20170824-1835-B873 Build date: 20170824-1835 Fell free to reopen, if it occurs again. > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Environment: windows > Reporter: Rob Stryker > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v3, windows > Fix For: 4.5.1.AM1 > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- 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