[JBoss JIRA] (WFCORE-3545) Composed keys don't have to be recognized by CLI
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3545?page=com.atlassian.jira.plugi... ]
Erich Duda reassigned WFCORE-3545:
----------------------------------
Assignee: Jean-Francois Denise (was: Erich Duda)
> Composed keys don't have to be recognized by CLI
> ------------------------------------------------
>
> Key: WFCORE-3545
> URL: https://issues.jboss.org/browse/WFCORE-3545
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 4.0.0.Alpha6
> Reporter: Erich Duda
> Assignee: Jean-Francois Denise
>
> Some keys like key down are composed from multiple characters. Normally when the key down is pushed, 3 characters are written into stdin. These 3 characters are read by InputStream::read operation at once and then decoded to the Key.DOWN constant.
> However there is no guarantee that InputStream::read operation returns all the 3 characters at once. It can return only first character and then remaining two. This actually happens in one test on Solaris and HPUX, where stdin is emulated by PipedInputStream.
> If the aforementioned situation happens, pushing of key down is decoded as pushing of two maybe three keys - ESC and some other key(s).
> The issue has low priority, because this behavior wasn't observed in real terminal with real input. It affects only testing.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (WFCORE-3545) Composed keys don't have to be recognized by CLI
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3545?page=com.atlassian.jira.plugi... ]
Erich Duda reassigned WFCORE-3545:
----------------------------------
Assignee: Erich Duda (was: Jean-Francois Denise)
> Composed keys don't have to be recognized by CLI
> ------------------------------------------------
>
> Key: WFCORE-3545
> URL: https://issues.jboss.org/browse/WFCORE-3545
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 4.0.0.Alpha6
> Reporter: Erich Duda
> Assignee: Erich Duda
>
> Some keys like key down are composed from multiple characters. Normally when the key down is pushed, 3 characters are written into stdin. These 3 characters are read by InputStream::read operation at once and then decoded to the Key.DOWN constant.
> However there is no guarantee that InputStream::read operation returns all the 3 characters at once. It can return only first character and then remaining two. This actually happens in one test on Solaris and HPUX, where stdin is emulated by PipedInputStream.
> If the aforementioned situation happens, pushing of key down is decoded as pushing of two maybe three keys - ESC and some other key(s).
> The issue has low priority, because this behavior wasn't observed in real terminal with real input. It affects only testing.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (WFCORE-3545) Composed keys don't have to be recognized by CLI
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3545?page=com.atlassian.jira.plugi... ]
Erich Duda closed WFCORE-3545.
------------------------------
Resolution: Done
> Composed keys don't have to be recognized by CLI
> ------------------------------------------------
>
> Key: WFCORE-3545
> URL: https://issues.jboss.org/browse/WFCORE-3545
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 4.0.0.Alpha6
> Reporter: Erich Duda
> Assignee: Jean-Francois Denise
>
> Some keys like key down are composed from multiple characters. Normally when the key down is pushed, 3 characters are written into stdin. These 3 characters are read by InputStream::read operation at once and then decoded to the Key.DOWN constant.
> However there is no guarantee that InputStream::read operation returns all the 3 characters at once. It can return only first character and then remaining two. This actually happens in one test on Solaris and HPUX, where stdin is emulated by PipedInputStream.
> If the aforementioned situation happens, pushing of key down is decoded as pushing of two maybe three keys - ESC and some other key(s).
> The issue has low priority, because this behavior wasn't observed in real terminal with real input. It affects only testing.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (WFCORE-3545) Composed keys don't have to be recognized by CLI
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3545?page=com.atlassian.jira.plugi... ]
Erich Duda reopened WFCORE-3545:
--------------------------------
> Composed keys don't have to be recognized by CLI
> ------------------------------------------------
>
> Key: WFCORE-3545
> URL: https://issues.jboss.org/browse/WFCORE-3545
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 4.0.0.Alpha6
> Reporter: Erich Duda
> Assignee: Jean-Francois Denise
>
> Some keys like key down are composed from multiple characters. Normally when the key down is pushed, 3 characters are written into stdin. These 3 characters are read by InputStream::read operation at once and then decoded to the Key.DOWN constant.
> However there is no guarantee that InputStream::read operation returns all the 3 characters at once. It can return only first character and then remaining two. This actually happens in one test on Solaris and HPUX, where stdin is emulated by PipedInputStream.
> If the aforementioned situation happens, pushing of key down is decoded as pushing of two maybe three keys - ESC and some other key(s).
> The issue has low priority, because this behavior wasn't observed in real terminal with real input. It affects only testing.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (WFCORE-3545) Composed keys don't have to be recognized by CLI
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3545?page=com.atlassian.jira.plugi... ]
Erich Duda commented on WFCORE-3545:
------------------------------------
This issue has wrong state. It should have status NEW. I will correct it.
> Composed keys don't have to be recognized by CLI
> ------------------------------------------------
>
> Key: WFCORE-3545
> URL: https://issues.jboss.org/browse/WFCORE-3545
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 4.0.0.Alpha6
> Reporter: Erich Duda
> Assignee: Jean-Francois Denise
>
> Some keys like key down are composed from multiple characters. Normally when the key down is pushed, 3 characters are written into stdin. These 3 characters are read by InputStream::read operation at once and then decoded to the Key.DOWN constant.
> However there is no guarantee that InputStream::read operation returns all the 3 characters at once. It can return only first character and then remaining two. This actually happens in one test on Solaris and HPUX, where stdin is emulated by PipedInputStream.
> If the aforementioned situation happens, pushing of key down is decoded as pushing of two maybe three keys - ESC and some other key(s).
> The issue has low priority, because this behavior wasn't observed in real terminal with real input. It affects only testing.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (WFCORE-3545) Composed keys don't have to be recognized by CLI
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3545?page=com.atlassian.jira.plugi... ]
Marek Kopecký commented on WFCORE-3545:
---------------------------------------
Test for down key is [here|https://github.com/wildfly/wildfly-core/blob/master/testsuite/standa...], needs to be uncommented after this issue will be fixed.
> Composed keys don't have to be recognized by CLI
> ------------------------------------------------
>
> Key: WFCORE-3545
> URL: https://issues.jboss.org/browse/WFCORE-3545
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 4.0.0.Alpha6
> Reporter: Erich Duda
> Assignee: Jean-Francois Denise
>
> Some keys like key down are composed from multiple characters. Normally when the key down is pushed, 3 characters are written into stdin. These 3 characters are read by InputStream::read operation at once and then decoded to the Key.DOWN constant.
> However there is no guarantee that InputStream::read operation returns all the 3 characters at once. It can return only first character and then remaining two. This actually happens in one test on Solaris and HPUX, where stdin is emulated by PipedInputStream.
> If the aforementioned situation happens, pushing of key down is decoded as pushing of two maybe three keys - ESC and some other key(s).
> The issue has low priority, because this behavior wasn't observed in real terminal with real input. It affects only testing.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months