[JBoss JIRA] (JBIDE-17264) Forge Console crashes when auto-completing values
by Ståle Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17264?page=com.atlassian.jira.plugi... ]
Ståle Pedersen edited comment on JBIDE-17264 at 8/20/14 8:02 PM:
-----------------------------------------------------------------
[~maxandersen] well, yes ofc its stuck when eclipse doesnt do what it is supposed to do :)
it looks like eclipse is acting like an ansi console, but it doesnt support the command for fetching the cursor position.
look at; http://www.termsys.demon.co.uk/vtansi.htm
when sending a {{<ESC>[6n}} æsh will lock until it receives data in the input stream like: {{<ESC>[{ROW};{COLUMN}R}}
tbh im not sure how needed it is for æsh to query the terminal if it has the correct cursor position, but i think its "good practice".
was (Author: stalep):
[~maxandersen] well, yes ofc its stuck when eclipse doesnt do what it is supposed to do :)
it looks like eclipse is acting like an ansi console, but it doesnt support the command for fetching the cursor position.
look at; http://www.termsys.demon.co.uk/vtansi.htm
when sending a <ESC>[6n æsh will lock until it receives data in the input stream like: <ESC>[{ROW};{COLUMN}R
tbh im not sure how needed it is for æsh to query the terminal if it has the correct cursor position, but i think its "good practice".
> Forge Console crashes when auto-completing values
> -------------------------------------------------
>
> Key: JBIDE-17264
> URL: https://issues.jboss.org/browse/JBIDE-17264
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: jstack.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17264) Forge Console crashes when auto-completing values
by Ståle Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17264?page=com.atlassian.jira.plugi... ]
Ståle Pedersen commented on JBIDE-17264:
----------------------------------------
[~maxandersen] well, yes ofc its stuck when eclipse doesnt do what it is supposed to do :)
it looks like eclipse is acting like an ansi console, but it doesnt support the command for fetching the cursor position.
look at; http://www.termsys.demon.co.uk/vtansi.htm
when sending a <ESC>[6n æsh will lock until it receives data in the input stream like: <ESC>[{ROW};{COLUMN}R
tbh im not sure how needed it is for æsh to query the terminal if it has the correct cursor position, but i think its "good practice".
> Forge Console crashes when auto-completing values
> -------------------------------------------------
>
> Key: JBIDE-17264
> URL: https://issues.jboss.org/browse/JBIDE-17264
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: jstack.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-18010) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18010?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18010:
---------------------------------------------
having this list on individual files is very noisy - it was done a lot in the past (~10+ years ago) but it becomes unmanageable and is much better represented in a notice file, recognition in blogs and our website and by looking in git history.
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18010
> URL: https://issues.jboss.org/browse/JBIDE-18010
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1: Please perform the following *2* tasks:
> 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
> Be sure to also include *translated* files, where they exist.
> *java files*
> {code:title=*.java}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> *html files*
> {code:title=about.html}
> © 2014 Red Hat, Inc. All rights reserved
> {code}
> *properties files*
> {code:title=about.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
> {code}
> {code:title=about_fr.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
> {code}
> {code:title=feature.properties}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> {code:title=Messages.properties}
> # Copyright (c) 2014 Red Hat, Inc. and others.
> {code}
> *xsd files*
> {code:title=jboss-as-naming_1_3.xsd}
> Copyright 2014, Red Hat, Inc., and individual contributors
> {code}
> 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
> Be sure to also include *translated* files, where they exist.
> *This step is particularly important for new plugins and features that have been added recently.*
> Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
> {code}BundleName = JMX Resources Bundle
> BundleProvider = JBoss by Red Hat{code}
> or
> {code}Bundle-Name.0 = JBossTools Archives Core Plugin
> Bundle-Vendor.0 = JBoss by Red Hat{code}
> Then in your MANIFEST.MF files, you will reference these variables like this.
> *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
> {code}Bundle-Localization: plugin
> Bundle-Name: %BundleName
> Bundle-Vendor: %BundleProvider{code}
> or
> {code}Bundle-Localization: plugin
> Bundle-Name: %Bundle-Name.0
> Bundle-Vendor: %Bundle-Vendor.0{code}
> For features, check that your *feature.properties* file contains good values too:
> {code}featureName=JMX Console
> featureProvider=JBoss by Red Hat{code}
> or
> {code}featureName=JBoss Archives Tools
> providerName=JBoss by Red Hat{code}
> Then in your feature.xml files, you will reference these variables like this:
> {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
> or
> {code}<feature label="%featureName" provider-name="%providerName" ...>{code}
> 3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
> 4. If you do not require QE to review your changes, please *Close* this JIRA when done.
> 5. If you have any questions, please contact [~nickboldt].
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3114
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17260) Review what we track via usage component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17260?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17260:
-----------------------------------
Summary: Review what we track via usage component (was: Review usage events)
> Review what we track via usage component
> ----------------------------------------
>
> Key: JBIDE-17260
> URL: https://issues.jboss.org/browse/JBIDE-17260
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: usage
> Reporter: Alexey Kazakov
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> We have introduced a few new events in JBT 4.2.0.Beta1 (server creation, central downloading) and a generic tracker of all used wizards in 4.2.0.Beta2. We should review if data collected is useful/too much/too little.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17264) Forge Console crashes when auto-completing values
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17264?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-17264:
-----------------------------------------
I also see this error in the logs (not sure if it's related to it):
{code}
!MESSAGE Error logged from Aesh Core Plugin:
!STACK 0
java.lang.Throwable: Unimplemented command: DEVICE_STATUS_REPORT
at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:17)
at org.jboss.tools.aesh.core.internal.io.DocumentHandler.handleCommand(DocumentHandler.java:41)
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.Console$ConsoleShell.getCursor(Console.java:968)
at org.jboss.aesh.console.AeshConsoleBuffer.redrawMultipleLines(AeshConsoleBuffer.java:170)
at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:128)
at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:113)
at org.jboss.aesh.console.AeshCompletionHandler.displayCompletion(AeshCompletionHandler.java:218)
at org.jboss.aesh.console.AeshCompletionHandler.complete(AeshCompletionHandler.java:142)
at org.jboss.aesh.console.AeshInputProcessor.complete(AeshInputProcessor.java:376)
at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:144)
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}
> Forge Console crashes when auto-completing values
> -------------------------------------------------
>
> Key: JBIDE-17264
> URL: https://issues.jboss.org/browse/JBIDE-17264
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: jstack.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months