[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21869:
---------------------------------------
[~fbricon] I have made progress as you can see in the following screen shot but I don't think the MessageConsole knows how to properly handle the control characters. Do you know if someone can confirm or advise how to do that:
!screenshot-1.png!
> 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: Jeff Cantrill
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
> Attachments: screenshot-1.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
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22038) Errors on startup with Java 9
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22038?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-22038:
---------------------------------------
The issue is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=466683 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=486213
The fix from https://bugs.eclipse.org/bugs/show_bug.cgi?id=466683#c19 doesn't work for some reason.
A workaround is to add -Dorg.osgi.framework.bundle.parent=ext
to eclipse.ini/jbdevstudio.ini.
However, I think Mars.2 won't work with a newer JDK9 build. It doesn't recognize JDK 9 build 111 as an installed JRE.
There is also a bug in Neon with a newer JDK 9 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=489958.
That's why Neon M6 doesn't work with JDK 9 build 111. The issue has been fixed in newer Neon builds.
> Errors on startup with Java 9
> -----------------------------
>
> Key: JBIDE-22038
> URL: https://issues.jboss.org/browse/JBIDE-22038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.1.CR1
> Reporter: Jan Richter
> Assignee: Snjezana Peco
> Fix For: 4.4.0.Alpha1
>
>
> Starting fresh JBT/JBDS with Java 9 results in an error dialog popping up with these two errors:
> {noformat}An internal error occurred during: "Update project wizard list".
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:38)
> at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:31)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator.getFavoriteExampleManager(ProjectExamplesActivator.java:1064)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.collectFavorites(GettingStartedHtmlPage.java:282)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.run(GettingStartedHtmlPage.java:273)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more{noformat}
> {noformat}An internal error occurred during: "Download quickstarts list".
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:396)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:273)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:263)
> at org.jboss.tools.project.examples.internal.ProjectExampleXmlProvider.getExamples(ProjectExampleXmlProvider.java:28)
> at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 7 more{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21984.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B260.
> Wrong Source Path when creating OS3 Server Adapter for multiple applications
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21984
> URL: https://issues.jboss.org/browse/JBIDE-21984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.CR1
>
> Attachments: launch_config.png, Screenshot 2016-03-31 14.34.47.png, server-adapter.png
>
>
> 1.
> !server-adapter.png|thumbnail!
> 2. Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config.
> !launch_config.png|thumbnail!
> Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app.
> The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3755) JBDS source zip: all files have 000 permissions after unzip
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3755?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3755:
-------------------------------------
Funnily enough, there is no readme in the zip ;)
{code}
$ find . -name 'README.how-to-build-from-sources-zip.txt'|wc -l
0
{code}
> JBDS source zip: all files have 000 permissions after unzip
> -----------------------------------------------------------
>
> Key: JBDS-3755
> URL: https://issues.jboss.org/browse/JBDS-3755
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Nick Boldt
>
> While verifying JBDS-3598 and trying to build from the latest source zip (jboss-devstudio-9.1.0.CR1-v20160326-0059-B443-src.zip), I hit a problem:
> When I unzipped the zip, I could not cd to the directory. It turned out that all the files had zero permissions. So I had to do "chmod -R 777 jboss-devstudio-9.1.0.CR1-src" first. Could we fix that?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3755) JBDS source zip: all files have 000 permissions after unzip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3755?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3755 at 4/1/16 10:13 AM:
-----------------------------------------------------------
"Note that file permissions will not be stored in the resulting zipfile." -- https://ant.apache.org/manual/Tasks/zip.html
So... this is a bug introduced during JBDS-3598 because the zip created by a maven mojo (with permissions) is updated here to add in a readme file (which removes the permissions):
{code}
<!-- JBDS-3598 add CSP src zip readme into src zip too -->
<copy todir="${project.build.directory}" overwrite="true">
<fileset file="${project.basedir}/../results/customer-portal/src.manual-instructions.txt" />
<mapper type="merge" to="README.how-to-build-from-sources-zip.txt" />
<filterchain>
<expandproperties />
</filterchain>
</copy>
<zip destfile="${project.build.directory}/jboss-devstudio-${parsedVersion.majorVersion}.${parsedVersion.minorVersion}.${parsedVersion.incrementalVersion}.${BUILD_ALIAS}-src.zip" whenempty="fail" update="true">
<zipfileset dir="${project.build.directory}/" includes="README.how-to-build-from-sources-zip.txt"/>
</zip>{code}
-- https://github.com/jbdevstudio/jbdevstudio-product/commit/e43a227464f9180...
was (Author: nickboldt):
"Note that file permissions will not be stored in the resulting zipfile." -- https://ant.apache.org/manual/Tasks/zip.html
So... this is a bug introduced during JBDS-3598 because the zip created by a maven mojo (with permissions) is updated here to add in a readme file (which removes the permissions):
{code}
<!-- JBDS-3598 add CSP src zip readme into src zip too -->
<copy todir="${project.build.directory}" overwrite="true">
<fileset file="${project.basedir}/../results/customer-portal/src.manual-instructions.txt" />
<mapper type="merge" to="README.how-to-build-from-sources-zip.txt" />
<filterchain>
<expandproperties />
</filterchain>
</copy>
<zip destfile="${project.build.directory}/jboss-devstudio-${parsedVersion.majorVersion}.${parsedVersion.minorVersion}.${parsedVersion.incrementalVersion}.${BUILD_ALIAS}-src.zip" whenempty="fail" update="true">
<zipfileset dir="${project.build.directory}/" includes="README.how-to-build-from-sources-zip.txt"/>
</zip>
{code}
-- https://github.com/jbdevstudio/jbdevstudio-product/commit/e43a227464f9180...
> JBDS source zip: all files have 000 permissions after unzip
> -----------------------------------------------------------
>
> Key: JBDS-3755
> URL: https://issues.jboss.org/browse/JBDS-3755
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Nick Boldt
>
> While verifying JBDS-3598 and trying to build from the latest source zip (jboss-devstudio-9.1.0.CR1-v20160326-0059-B443-src.zip), I hit a problem:
> When I unzipped the zip, I could not cd to the directory. It turned out that all the files had zero permissions. So I had to do "chmod -R 777 jboss-devstudio-9.1.0.CR1-src" first. Could we fix that?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3755) JBDS source zip: all files have 000 permissions after unzip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3755?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3755:
----------------------------------
We'd need to either remove the readme (which is also up on the CSP accompanying the src.zip so the zip retains correct file permissions) or migrate the two ant tasks (one to expand variables in the txt file, then another to insert the file into the zip) to be part of the fetch-sources-from-manifests mojo task so it's not limited by Ant's permissionless Zip task.
--
Since sources are now publically available at https://github.com/jbdevstudio/jbdevstudio-product/ I'm inclined to *simply remove the readme file*.
We could also *REMOVE this zip from the distribution on CSP* and replace it with a README saying "sources are here: https://github.com/jbdevstudio/jbdevstudio-product/ ".
[~akazakov] [~maxandersen] WDYT?
> JBDS source zip: all files have 000 permissions after unzip
> -----------------------------------------------------------
>
> Key: JBDS-3755
> URL: https://issues.jboss.org/browse/JBDS-3755
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Nick Boldt
>
> While verifying JBDS-3598 and trying to build from the latest source zip (jboss-devstudio-9.1.0.CR1-v20160326-0059-B443-src.zip), I hit a problem:
> When I unzipped the zip, I could not cd to the directory. It turned out that all the files had zero permissions. So I had to do "chmod -R 777 jboss-devstudio-9.1.0.CR1-src" first. Could we fix that?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3755) JBDS source zip: all files have 000 permissions after unzip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3755?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3755 at 4/1/16 10:08 AM:
-----------------------------------------------------------
"Note that file permissions will not be stored in the resulting zipfile." -- https://ant.apache.org/manual/Tasks/zip.html
So... this is a bug introduced during JBDS-3598 because the zip created by a maven mojo (with permissions) is updated here to add in a readme file (which removes the permissions):
{code}
<!-- JBDS-3598 add CSP src zip readme into src zip too -->
<copy todir="${project.build.directory}" overwrite="true">
<fileset file="${project.basedir}/../results/customer-portal/src.manual-instructions.txt" />
<mapper type="merge" to="README.how-to-build-from-sources-zip.txt" />
<filterchain>
<expandproperties />
</filterchain>
</copy>
<zip destfile="${project.build.directory}/jboss-devstudio-${parsedVersion.majorVersion}.${parsedVersion.minorVersion}.${parsedVersion.incrementalVersion}.${BUILD_ALIAS}-src.zip" whenempty="fail" update="true">
<zipfileset dir="${project.build.directory}/" includes="README.how-to-build-from-sources-zip.txt"/>
</zip>
{code}
-- https://github.com/jbdevstudio/jbdevstudio-product/commit/e43a227464f9180...
was (Author: nickboldt):
"Note that file permissions will not be stored in the resulting zipfile." -- https://ant.apache.org/manual/Tasks/zip.html
So... this is a bug introduced during JBDS-3598 because the zip created by a maven mojo (with permissions) is updated here to add in a readme file:
{code}
<!-- JBDS-3598 add CSP src zip readme into src zip too -->
<copy todir="${project.build.directory}" overwrite="true">
<fileset file="${project.basedir}/../results/customer-portal/src.manual-instructions.txt" />
<mapper type="merge" to="README.how-to-build-from-sources-zip.txt" />
<filterchain>
<expandproperties />
</filterchain>
</copy>
<zip destfile="${project.build.directory}/jboss-devstudio-${parsedVersion.majorVersion}.${parsedVersion.minorVersion}.${parsedVersion.incrementalVersion}.${BUILD_ALIAS}-src.zip" whenempty="fail" update="true">
<zipfileset dir="${project.build.directory}/" includes="README.how-to-build-from-sources-zip.txt"/>
</zip>
{code}
-- https://github.com/jbdevstudio/jbdevstudio-product/commit/e43a227464f9180...
> JBDS source zip: all files have 000 permissions after unzip
> -----------------------------------------------------------
>
> Key: JBDS-3755
> URL: https://issues.jboss.org/browse/JBDS-3755
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Nick Boldt
>
> While verifying JBDS-3598 and trying to build from the latest source zip (jboss-devstudio-9.1.0.CR1-v20160326-0059-B443-src.zip), I hit a problem:
> When I unzipped the zip, I could not cd to the directory. It turned out that all the files had zero permissions. So I had to do "chmod -R 777 jboss-devstudio-9.1.0.CR1-src" first. Could we fix that?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3755) JBDS source zip: all files have 000 permissions after unzip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3755?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3755:
----------------------------------
"Note that file permissions will not be stored in the resulting zipfile." -- https://ant.apache.org/manual/Tasks/zip.html
So... this is a bug introduced during JBDS-3598 because the zip created by a maven mojo (with permissions) is updated here to add in a readme file:
{code}
<!-- JBDS-3598 add CSP src zip readme into src zip too -->
<copy todir="${project.build.directory}" overwrite="true">
<fileset file="${project.basedir}/../results/customer-portal/src.manual-instructions.txt" />
<mapper type="merge" to="README.how-to-build-from-sources-zip.txt" />
<filterchain>
<expandproperties />
</filterchain>
</copy>
<zip destfile="${project.build.directory}/jboss-devstudio-${parsedVersion.majorVersion}.${parsedVersion.minorVersion}.${parsedVersion.incrementalVersion}.${BUILD_ALIAS}-src.zip" whenempty="fail" update="true">
<zipfileset dir="${project.build.directory}/" includes="README.how-to-build-from-sources-zip.txt"/>
</zip>
{code}
-- https://github.com/jbdevstudio/jbdevstudio-product/commit/e43a227464f9180...
> JBDS source zip: all files have 000 permissions after unzip
> -----------------------------------------------------------
>
> Key: JBDS-3755
> URL: https://issues.jboss.org/browse/JBDS-3755
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Nick Boldt
>
> While verifying JBDS-3598 and trying to build from the latest source zip (jboss-devstudio-9.1.0.CR1-v20160326-0059-B443-src.zip), I hit a problem:
> When I unzipped the zip, I could not cd to the directory. It turned out that all the files had zero permissions. So I had to do "chmod -R 777 jboss-devstudio-9.1.0.CR1-src" first. Could we fix that?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3757) Add some logging to setup routines
by Jan Richter (JIRA)
Jan Richter created JBDS-3757:
---------------------------------
Summary: Add some logging to setup routines
Key: JBDS-3757
URL: https://issues.jboss.org/browse/JBDS-3757
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
Assignee: Denis Golovin
We should log events in setup the same way we now do in download and install phases. For example when the install -> setup transition happens, when setup is fired for an already existing item.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21869:
---------------------------------------
Some side investigation I found the MessageConsole allows for setting an encoding type. Worth investigating if this resolves the issue
> 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: Jeff Cantrill
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> 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
(v6.4.11#64026)
10 years