[JBoss JIRA] (JBIDE-18178) Forge Console throws exception when UP is kept pressed for some time
by George Gastaldi (JIRA)
George Gastaldi created JBIDE-18178:
---------------------------------------
Summary: Forge Console throws exception when UP is kept pressed for some time
Key: JBIDE-18178
URL: https://issues.jboss.org/browse/JBIDE-18178
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Reporter: George Gastaldi
Priority: Blocker
Fix For: 4.2.x
{code}
java.lang.Throwable: Unimplemented command: CURSOR_UP
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:18)
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:22)
at org.jboss.tools.aesh.core.internal.io.DocumentInputOutputHandler.handleCommand(DocumentInputOutputHandler.java:42)
at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:50)
at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:27)
at java.io.PrintStream.write(PrintStream.java:480)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
at java.io.PrintStream.write(PrintStream.java:527)
at java.io.PrintStream.print(PrintStream.java:669)
at org.jboss.aesh.console.AeshConsoleBuffer.redrawMultipleLines(AeshConsoleBuffer.java:207)
at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:128)
at org.jboss.aesh.console.AeshInputProcessor.getHistoryElement(AeshInputProcessor.java:420)
at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:164)
at org.jboss.aesh.console.Console.processInternalOperation(Console.java:615)
at org.jboss.aesh.console.Console.execute(Console.java:605)
at org.jboss.aesh.console.Console.access$700(Console.java:58)
at org.jboss.aesh.console.Console$6.run(Console.java:508)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18093) Explorer: Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS/Explorer
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-18093:
-------------------------------------------------
Brenton Leanhardt <bleanhar(a)redhat.com> changed the Status of [bug 1122089|https://bugzilla.redhat.com/show_bug.cgi?id=1122089] from CLOSED to ASSIGNED
> Explorer: Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS/Explorer
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18093
> URL: https://issues.jboss.org/browse/JBIDE-18093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: explorer
> Fix For: 4.2.0.CR1
>
> Attachments: illegal-character.png, mock1b.png, special-character-mock-cartridges.png
>
>
> Description of problem:
> I have developed a custom cartridge for OSE and placed the special character "®" (registered trademark) in the description field within my "manifest.yml". The cartridge could be installed correctly via WebUI and was also working fine from a technical point of view.
> However, when trying to access the OSE instance from JBDS via the Openshift Explorer plugin, I always got the following error:
> Invalid value for input string: "00ae"
> The string "00ae" is the unicode representation of my special character. After removing everything worked fine again. The OpenShift Explorer was completely unusable in this scenario! So only one installed cartridge with this special character can poison a whole installation and affect ALL users!!!
> Version-Release number of selected component (if applicable):
> OSE 2.2 (Developer Image)
> How reproducible:
> Yes.
> Steps to Reproduce:
> 1. Create a custom cartridge and add a "®" to the description field of your manifest.yml.
> 2. Install the cartridge according to doc.
> 3. Start JBDS and try to work with your OSE instance via the OpenShift Explorer plugin (e.g. try to add an application)
> Result:
> !illegal-character.png!
> The Eclipse log shows the following snippet:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2014-08-28 03:02:54.101
> !MESSAGE An internal error occurred during: "Loading OpenShift information...".
> !STACK 0
> java.lang.NumberFormatException: For input string: "00ae"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:492)
> at java.lang.Integer.parseInt(Integer.java:527)
> at org.jboss.dmr.JSONParserImpl.parseStringValue(JSONParserImpl.java:109)
> at org.jboss.dmr.JSONParser.yyLex(JSONParser.java:574)
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:650)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1184)
> at com.openshift.internal.client.response.OpenShiftJsonDTOFactory.getModelNode(OpenShiftJsonDTOFactory.java:207)
> at com.openshift.internal.client.response.OpenShiftJsonDTOFactory.get(OpenShiftJsonDTOFactory.java:94)
> at com.openshift.internal.client.RestService.request(RestService.java:124)
> at com.openshift.internal.client.RestService.request(RestService.java:103)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:155)
> at com.openshift.internal.client.DomainResource$ListApplicationsRequest.execute(DomainResource.java:446)
> at com.openshift.internal.client.DomainResource.updateApplications(DomainResource.java:297)
> at com.openshift.internal.client.DomainResource.refresh(DomainResource.java:381)
> at org.jboss.tools.openshift.express.internal.ui.command.RefreshResourceHandler$1.doRun(RefreshResourceHandler.java:69)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> To create the cartridge with the illegal character do the following as stated in the bugzilla:
> {quote}
> 1. Modify the official EAP Cartridge by adding a '®' to the description: (I've attached my manifest.yml)
> vi /usr/libexec/openshift/cartridges/jbosseap/metadata/manifest.yml
> 2. Reinstall cartridge with the following commands:
> cd /usr/libexec/openshift/cartridges
> oo-admin-cartridge --action install --recursive --source /usr/libexec/openshift/cartridges
> oo-admin-ctl-cartridge --activate -c import-node --obsolete
> oo-admin-broker-cache --clear && oo-admin-console-cache --clear
> 3. Create a new gear based on EAP cartridge.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18093) Explorer: Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS/Explorer
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-18093:
-------------------------------------------------
Brenton Leanhardt <bleanhar(a)redhat.com> changed the Status of [bug 1122089|https://bugzilla.redhat.com/show_bug.cgi?id=1122089] from ASSIGNED to CLOSED
> Explorer: Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS/Explorer
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18093
> URL: https://issues.jboss.org/browse/JBIDE-18093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: explorer
> Fix For: 4.2.0.CR1
>
> Attachments: illegal-character.png, mock1b.png, special-character-mock-cartridges.png
>
>
> Description of problem:
> I have developed a custom cartridge for OSE and placed the special character "®" (registered trademark) in the description field within my "manifest.yml". The cartridge could be installed correctly via WebUI and was also working fine from a technical point of view.
> However, when trying to access the OSE instance from JBDS via the Openshift Explorer plugin, I always got the following error:
> Invalid value for input string: "00ae"
> The string "00ae" is the unicode representation of my special character. After removing everything worked fine again. The OpenShift Explorer was completely unusable in this scenario! So only one installed cartridge with this special character can poison a whole installation and affect ALL users!!!
> Version-Release number of selected component (if applicable):
> OSE 2.2 (Developer Image)
> How reproducible:
> Yes.
> Steps to Reproduce:
> 1. Create a custom cartridge and add a "®" to the description field of your manifest.yml.
> 2. Install the cartridge according to doc.
> 3. Start JBDS and try to work with your OSE instance via the OpenShift Explorer plugin (e.g. try to add an application)
> Result:
> !illegal-character.png!
> The Eclipse log shows the following snippet:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2014-08-28 03:02:54.101
> !MESSAGE An internal error occurred during: "Loading OpenShift information...".
> !STACK 0
> java.lang.NumberFormatException: For input string: "00ae"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:492)
> at java.lang.Integer.parseInt(Integer.java:527)
> at org.jboss.dmr.JSONParserImpl.parseStringValue(JSONParserImpl.java:109)
> at org.jboss.dmr.JSONParser.yyLex(JSONParser.java:574)
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:650)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1184)
> at com.openshift.internal.client.response.OpenShiftJsonDTOFactory.getModelNode(OpenShiftJsonDTOFactory.java:207)
> at com.openshift.internal.client.response.OpenShiftJsonDTOFactory.get(OpenShiftJsonDTOFactory.java:94)
> at com.openshift.internal.client.RestService.request(RestService.java:124)
> at com.openshift.internal.client.RestService.request(RestService.java:103)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:155)
> at com.openshift.internal.client.DomainResource$ListApplicationsRequest.execute(DomainResource.java:446)
> at com.openshift.internal.client.DomainResource.updateApplications(DomainResource.java:297)
> at com.openshift.internal.client.DomainResource.refresh(DomainResource.java:381)
> at org.jboss.tools.openshift.express.internal.ui.command.RefreshResourceHandler$1.doRun(RefreshResourceHandler.java:69)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> To create the cartridge with the illegal character do the following as stated in the bugzilla:
> {quote}
> 1. Modify the official EAP Cartridge by adding a '®' to the description: (I've attached my manifest.yml)
> vi /usr/libexec/openshift/cartridges/jbosseap/metadata/manifest.yml
> 2. Reinstall cartridge with the following commands:
> cd /usr/libexec/openshift/cartridges
> oo-admin-cartridge --action install --recursive --source /usr/libexec/openshift/cartridges
> oo-admin-ctl-cartridge --activate -c import-node --obsolete
> oo-admin-broker-cache --clear && oo-admin-console-cache --clear
> 3. Create a new gear based on EAP cartridge.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18157) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18157?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-18157.
----------------------------------
Assignee: Alexey Kazakov
Resolution: Done
> For JBIDE 4.2.0.CR1: Code Freeze + Branch [Base]
> ------------------------------------------------
>
> Key: JBIDE-18157
> URL: https://issues.jboss.org/browse/JBIDE-18157
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Mickael Istria
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18174) cdi.ui tests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18174?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-18174:
--------------------------------------
Assignee: Victor Rubezhny (was: Alexey Kazakov)
> cdi.ui tests failure
> --------------------
>
> Key: JBIDE-18174
> URL: https://issues.jboss.org/browse/JBIDE-18174
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
>
> {code}
> Failed tests: testCAELProposalFilteringInXHTML(org.jboss.tools.cdi.ui.test.CAELProposalFilteringTest): Content Assistant returned no proposals
> testCAELProposalFilteringInJSP(org.jboss.tools.cdi.ui.test.CAELProposalFilteringTest): Content Assistant returned no proposals
> testEL(org.jboss.tools.cdi.ui.test.CATest): Content Assistant returned no proposals
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18174) cdi.ui tests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18174?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18174:
----------------------------------------
Looks like problems with tests. I can't reproduce these problems when testing manually. I also don't see that these test are invoking CDI content assist. So looks like there is some problem with the way we invoke content assist in the tests.
> cdi.ui tests failure
> --------------------
>
> Key: JBIDE-18174
> URL: https://issues.jboss.org/browse/JBIDE-18174
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.CR1
>
>
> {code}
> Failed tests: testCAELProposalFilteringInXHTML(org.jboss.tools.cdi.ui.test.CAELProposalFilteringTest): Content Assistant returned no proposals
> testCAELProposalFilteringInJSP(org.jboss.tools.cdi.ui.test.CAELProposalFilteringTest): Content Assistant returned no proposals
> testEL(org.jboss.tools.cdi.ui.test.CATest): Content Assistant returned no proposals
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months