[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-21869:
----------------------------------------
Assignee: Andre Dietisheim (was: Jeff Cantrill)
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.4.3.AM2
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22228) NPE when deploying to Openshift EAP
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22228?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22228:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.x)
> NPE when deploying to Openshift EAP
> -----------------------------------
>
> Key: JBIDE-22228
> URL: https://issues.jboss.org/browse/JBIDE-22228
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Environment: Windows 10
> Reporter: Thomas Mäder
> Assignee: Jeff MAURY
> Fix For: 4.4.3.AM2
>
>
> When I try to publish to an EAP in the CDK, I get a NullPointerException:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:309)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:298)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:390)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:87)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> 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:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-21849:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.x)
> [AP] Not able to list services under a project after login to AP
> ----------------------------------------------------------------
>
> Key: JBIDE-21849
> URL: https://issues.jboss.org/browse/JBIDE-21849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191
> -AP puddle: 2016-03-09.2
> -oc version:
> oc v3.2.0.1
> kubernetes v1.2.0-alpha.7-703-gbc4550d
> Reporter: Xia Zhao
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.3.AM2
>
>
> -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}"
> -Issue did not repro if switch to OSE
> -Repro on Linux/Windows/Mac OS
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-21849:
----------------------------------------
Assignee: Andre Dietisheim
> [AP] Not able to list services under a project after login to AP
> ----------------------------------------------------------------
>
> Key: JBIDE-21849
> URL: https://issues.jboss.org/browse/JBIDE-21849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191
> -AP puddle: 2016-03-09.2
> -oc version:
> oc v3.2.0.1
> kubernetes v1.2.0-alpha.7-703-gbc4550d
> Reporter: Xia Zhao
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.3.AM2
>
>
> -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}"
> -Issue did not repro if switch to OSE
> -Repro on Linux/Windows/Mac OS
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-21719:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.x)
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.3.AM2
>
> Attachments: JBossPerspective_PropertiesMayBeWider.png, jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3595) dark theme not nice
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3595?page=com.atlassian.jira.plugin.... ]
Dmitrii Bocharov updated JBDS-3595:
-----------------------------------
Fix Version/s: LATER
(was: 10.x)
> dark theme not nice
> -------------------
>
> Key: JBDS-3595
> URL: https://issues.jboss.org/browse/JBDS-3595
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 9.1.0.Beta2
> Reporter: Aleksandar Kostadinov
> Priority: Minor
> Fix For: LATER
>
> Attachments: jbds_dark.png
>
>
> Selecting "Dark" them in appearance yields somehow ugly result. Would be nice to be fixed.
> !jbds_dark.png|thumbnail!
> btw have installed GoClipse, not sure if that matters. Have not checked dark theme before install.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23757) Thread deadlock when starting Eclipse
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23757?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-23757:
-----------------------------------
Assignee: Rob Stryker
> Thread deadlock when starting Eclipse
> -------------------------------------
>
> Key: JBIDE-23757
> URL: https://issues.jboss.org/browse/JBIDE-23757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.Final
> Environment: MacOS Sierra, JDK 1.8.0_112
> Reporter: Jon Kranes
> Assignee: Rob Stryker
> Fix For: 4.4.3.Final
>
>
> Steps to reproduce:
> * Install latest Eclipse (Neon 4.6.2) (also tested with Spring ToolSuite 3.8.3 with same result)
> * Install JBoss AS, Wildfly & EAP Server Tools from JBoss Tools 4.4.2 Final
> * Add Wildfly 10.x runtime to Eclipse (tested 10.0 and 10.1 with same results)
> * Add Wildfly 10.x server to Eclipse
> * Create a default Maven Web App project
> * Add the web app project to the Wildfly server
> * Exit Eclipse and restart
> Eclipse hangs on startup with a thread deadlock. Eclipse "Progress" window shows "Registering Listeners" which never completes and blocks other Eclipse startup tasks. At this point Eclipse cannot exit and must be force-quit.
> Thread dump output from jvisualvm shows a thread deadlock:
> Found one Java-level deadlock:
> =============================
> "Thread-8":
> waiting to lock monitor 0x000000011fe4e758 (object 0x0000000782b7aa00, a org.eclipse.wst.server.core.internal.Server),
> which is held by "Worker-0"
> "Worker-0":
> waiting to lock monitor 0x0000000101a566e8 (object 0x0000000782b7aa70, a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager),
> which is held by "Thread-8"
> Java stack information for the threads listed above:
> ===================================================
> "Thread-8":
> at org.eclipse.wst.server.core.internal.Server.getServerNotificationManager(Server.java:1034)
> - waiting to lock <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.removeServerListener(Server.java:697)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.protectAddManagerAsListeners(UnitedServerListenerManager.java:152)
> - locked <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.initializeManager(UnitedServerListenerManager.java:81)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.access$1(UnitedServerListenerManager.java:73)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager$1.run(UnitedServerListenerManager.java:68)
> "Worker-0":
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.addListener(UnitedServerListenerManager.java:109)
> - waiting to lock <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start(JBossServerCorePlugin.java:74)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.wst.server.core.internal.ServerType.createServerDelegate(ServerType.java:91)
> at org.eclipse.wst.server.core.internal.Server.getDelegate(Server.java:506)
> - locked <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.getChildModules(Server.java:2634)
> at org.eclipse.wst.server.core.internal.Server.visitModule(Server.java:3058)
> at org.eclipse.wst.server.core.internal.Server.visit(Server.java:3039)
> at org.eclipse.wst.server.core.internal.Server.getAllModules(Server.java:1542)
> at org.eclipse.wst.server.ui.internal.cnf.ServersView2$3.run(ServersView2.java:189)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Found 1 deadlock.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
