[
https://issues.jboss.org/browse/FORGE-593?page=com.atlassian.jira.plugin....
]
Vineet Reynolds commented on FORGE-593:
---------------------------------------
Just adding a comment about how this was fixed, so we're not confused by the earlier
comment about an older proposed fix:
The blocking queue in ConsoleInputSession is converted to a static shared queue to ensure
that characters input by a user that are captured by an eventually terminating reader
thread will not be lost (by pushing them in a per-thread queue). Instead, the characters
are now pushed into a shared queue where they may be read without any loss.
This is a hack to ensure that characters are not lost. Ideally, in a multiple reader
thread situation, this should have been done by ensuring that the reader thread obtained
just the right number of characters from System.in and eventually terminated gracefully.
But, reads on System.in are blocking by nature, and Windows does not provide information
on the
number of characters to be read via InputStream.available(). Hence the hack.
Forge swallows first character of user input after restarting
(typically from plugin installation)
--------------------------------------------------------------------------------------------------
Key: FORGE-593
URL:
https://issues.jboss.org/browse/FORGE-593
Project: Forge
Issue Type: Bug
Components: UI - Shell
Affects Versions: 1.0.5.Final
Reporter: Lincoln Baxter III
Assignee: Vineet Reynolds
Labels: annoying
Fix For: 1.3.3.Final
Attachments: threaddump-1373073105033.tdump
'forge install-plugin openshift'
Then type something. The first character you type will not be displayed or read.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira