[jboss-as7-dev] Characters not echoing back to terminal after running AS7 testsuite

[Alexey Loubyansky]

Yes, if I create a simple subclass of jline.Terminal and just leave 
initializeTerminal() empty (where the stty changes happen) I don't see 
the issue any more. But of course then the interactive mode suffers.

On 04/29/2012 08:38 PM, Jason Greene wrote:
> Looking at the JLine code it seems we could create a FakeTerminal (extends Terminal), and call ConsoleReader with that and a normal set of streams. Then it won't mess with the TTY and would be completely virtual.
>
> Sent from my iPhone
>
> On Apr 29, 2012, at 11:35 AM, Alexey Loubyansky<alexey.loubyansky at redhat.com>  wrote:
>
>> It might work as a quick fix.
>>
>> I am looking into switching from the IO-based tests to the CLI API. They
>> will be cleaner looking and run faster. But it's not possible for all
>> the tests. So, until this is all figured out we could reset the terminal
>> "just in case".
>>
>> Alexey
>>
>> On 04/29/2012 09:50 AM, Tristan Tarrant wrote:
>>> We can minimize the impact of this by resetting the tty state using stty
>>> in the shell script used to launch the CLI (since people will probably
>>> kill -9 the java process and not the parent shell).
>>>
>>> Tristan
>>>
>>> On 04/28/2012 07:48 AM, Stuart Douglas wrote:
>>>> That would be because kill -9 does not give the shutdown hook that restores the terminal a chance to run.
>>>>
>>>> Stuart
>>>>
>>>>
>>>> On 28/04/2012, at 9:44 PM, Kabir Khan wrote:
>>>>
>>>>> I also see something similar if I
>>>>> *Start AS in terminal 1
>>>>> *Connect with cli in terminal 2
>>>>> *killall -9 java in terminal 3
>>>>>
>>>>> ->    Terminal 2 does not echo characters
>>>>> On 27 Apr 2012, at 19:01, Brian Stansberry wrote:
>>>>>
>>>>>> A number of people are reporting that after building the current
>>>>>> upstream master and running the testsuite, the terminal used to do that
>>>>>> no longer echos characters you type back to the screen.
>>>>>>
>>>>>> Just wanted to let you know we're aware of the issue and are working it,
>>>>>> with a pretty good idea as to the root cause.
>>>>>>
>>>>>> Some solutions people have used to get a normally functioning terminal
>>>>>> after this happens:
>>>>>>
>>>>>> 1) The Reset command from the Terminal menu.
>>>>>> 2) Running 'stty sane' from the command line
>>>>>> 3) Open a new terminal. ;)
>>>>>>
>>>>>> --
>>>>>> Brian Stansberry
>>>>>> Principal Software Engineer
>>>>>> JBoss by Red Hat
>>>>>> _______________________________________________
>>>>>> jboss-as7-dev mailing list
>>>>>> jboss-as7-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev