[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21869:
---------------------------------------
[~jcantrill] command line shows output correctly. Pattern for encoding issue is at first one occurrence, than two occurrences of following string (I use � as substitution of the weird character)
{code}�[0m{code}
> 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.x
>
> 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
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-693) Create new smoke tests for Drools plugin test suite
by Tomas David (JIRA)
Tomas David created JBTIS-693:
---------------------------------
Summary: Create new smoke tests for Drools plugin test suite
Key: JBTIS-693
URL: https://issues.jboss.org/browse/JBTIS-693
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: drools/ jBPM, QE
Reporter: Tomas David
Assignee: Tomas David
Create at least two smoke tests:
* create new project smoke test
* open kie navigator view smoke test
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3698) Installer - We should document (rel notes) the versions of the installable components that we support
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3698?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3698:
-----------------------------------
I'm fine with the note. As far as JIRAs go, the only related one I could find is JBDS-3836 and that is mostly about misleading UI in this case.
> Installer - We should document (rel notes) the versions of the installable components that we support
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-3698
> URL: https://issues.jboss.org/browse/JBDS-3698
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Task
> Components: documentation, platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Labels: havoc
> Fix For: 10.0.0.Alpha3
>
>
> It's good that the installer will allow users to have/retain their own installed components, and verify that the installed versions are supported, but we should provide the users with a documented list of the ranges of supported versions. Thx!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3696) Browse buttons should not respond when a file dialog is opened
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3696?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3696:
-----------------------------------
Assignee: Denis Golovin (was: Joshua Wilson)
Resolution: Done
> Browse buttons should not respond when a file dialog is opened
> --------------------------------------------------------------
>
> Key: JBDS-3696
> URL: https://issues.jboss.org/browse/JBDS-3696
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 10.0.0.Alpha3
>
>
> Clicking the 'Browse' buttons on confirm page opens a native file dialog. Once open, the user can just navigate back to the main window and keep clicking those buttons. What happens is - for every click a new dialog is queued up. Once the current one closes the next one in the queue will open. We should not allow this kind of chaining - it is fairly annoying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3696) Browse buttons should not respond when a file dialog is opened
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3696?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3696:
--------------------------------
> Browse buttons should not respond when a file dialog is opened
> --------------------------------------------------------------
>
> Key: JBDS-3696
> URL: https://issues.jboss.org/browse/JBDS-3696
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Joshua Wilson
> Labels: havoc, ui
> Fix For: 10.0.0.Alpha3
>
>
> Clicking the 'Browse' buttons on confirm page opens a native file dialog. Once open, the user can just navigate back to the main window and keep clicking those buttons. What happens is - for every click a new dialog is queued up. Once the current one closes the next one in the queue will open. We should not allow this kind of chaining - it is fairly annoying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3696) Browse buttons should not respond when a file dialog is opened
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3696?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3696:
--------------------------------
> Browse buttons should not respond when a file dialog is opened
> --------------------------------------------------------------
>
> Key: JBDS-3696
> URL: https://issues.jboss.org/browse/JBDS-3696
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Joshua Wilson
> Labels: havoc, ui
> Fix For: 10.0.0.Alpha3
>
>
> Clicking the 'Browse' buttons on confirm page opens a native file dialog. Once open, the user can just navigate back to the main window and keep clicking those buttons. What happens is - for every click a new dialog is queued up. Once the current one closes the next one in the queue will open. We should not allow this kind of chaining - it is fairly annoying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3696) Browse buttons should not respond when a file dialog is opened
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3696?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3696:
--------------------------------
> Browse buttons should not respond when a file dialog is opened
> --------------------------------------------------------------
>
> Key: JBDS-3696
> URL: https://issues.jboss.org/browse/JBDS-3696
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Joshua Wilson
> Labels: havoc, ui
> Fix For: 10.0.0.Alpha3
>
>
> Clicking the 'Browse' buttons on confirm page opens a native file dialog. Once open, the user can just navigate back to the main window and keep clicking those buttons. What happens is - for every click a new dialog is queued up. Once the current one closes the next one in the queue will open. We should not allow this kind of chaining - it is fairly annoying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3696) Browse buttons should not respond when a file dialog is opened
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3696?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3696:
--------------------------------
> Browse buttons should not respond when a file dialog is opened
> --------------------------------------------------------------
>
> Key: JBDS-3696
> URL: https://issues.jboss.org/browse/JBDS-3696
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Joshua Wilson
> Labels: havoc, ui
> Fix For: 10.0.0.Alpha3
>
>
> Clicking the 'Browse' buttons on confirm page opens a native file dialog. Once open, the user can just navigate back to the main window and keep clicking those buttons. What happens is - for every click a new dialog is queued up. Once the current one closes the next one in the queue will open. We should not allow this kind of chaining - it is fairly annoying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months