Bug 1035856

Summary: Cli is showing wrong commands while browsing cli history via up & down key
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Petr Kremensky <pkremens>
Component: CLIAssignee: Alexey Loubyansky <olubyans>
Status: CLOSED WORKSFORME QA Contact: Petr Kremensky <pkremens>
Severity: medium Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: brian.stansberry, ewertz, hhovsepy, spederse
Target Milestone: ---   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-15 10:02:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Petr Kremensky 2013-11-28 16:26:03 UTC 
Description of problem:
 One can run into some wrong output while browsing commands history via UP & DOWN keys.

Version-Release number of selected component (if applicable):
 EAP 6.2.0.CR3

How reproducible:
 Always

Steps to Reproduce:
 1. Start standalone server and connect to CLI.
 2. Run the following two commands:
/subsystem=ee:read-attribute(name=spec-descriptor-property-replacement)
/subsystem=ee:read-attribute(name=jboss-descriptor-property-replacement)
 3. Press the Up key to get on first command.

Actual results:
1.UP - /subsystem=ee:read-attribute(name=jboss-descriptor-property-replacement)
// note the missing ending bracket
2.UP - /subsystem=ee:read-attribute(name=jboss-descriptor-property-replacement

Expected results:
1.UP - /subsystem=ee:read-attribute(name=jboss-descriptor-property-replacement)
2.UP - /subsystem=ee:read-attribute(name=spec-descriptor-property-replacement)

Additional info:
 - CLI will behave as expected once I remove closing bracket from one of the commands
Comment 1 Ståle W. Pedersen 2013-11-28 21:12:15 UTC 
hi, i can confirm that this is a æsh bug. ill fix it early next week.
btw, the history is correct, it is just not displayed correctly.
Comment 2 Ståle W. Pedersen 2013-11-29 00:29:58 UTC 
https://issues.jboss.org/browse/AESH-172
Comment 3 Ståle W. Pedersen 2013-11-29 00:52:46 UTC 
ive pushed out version 0.33.11 of aesh that solves this issue.
Comment 4 Joe Wertz 2014-05-15 10:02:17 UTC 
Verified fixed in 6.3.