Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 1.0.0.CR4, 2.0.0.Alpha1
Affects Version/s: None
Component/s: CLI
Labels:
None

Steps to Reproduce:
Hide

On Linux Machine:

1. Create a file in user home directory with name ".inputrc"

2. Add the following entry inside the file ".inputrc"

# Control characters "\C-?": backward-delete-char

3. Start jboss cli script.
Show
On Linux Machine: 1. Create a file in user home directory with name ".inputrc" 2. Add the following entry inside the file ".inputrc" # Control characters "\C-?" : backward-delete- char 3. Start jboss cli script.
Git Pull Request:
https://github.com/wildfly/wildfly-core/pull/577, https://github.com/wildfly/wildfly-core/pull/717, https://github.com/wildfly/wildfly-core/pull/716
Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=1203997

When using [wildfly-8.2.0.Final] When user has a '.inputrc' in the user home directory with the following content:

# Control characters
"\C-?":   backward-delete-char

The it fails with the the following Stack Trace:

./jboss-cli.sh 
java.lang.RuntimeException: ERROR parsing ? keys to aesh. Check your inputrc.
	at org.jboss.aesh.edit.mapper.KeyMapper.convertRandomControlKeys(KeyMapper.java:161)
	at org.jboss.aesh.edit.mapper.KeyMapper.mapRandomKeys(KeyMapper.java:138)
	at org.jboss.aesh.edit.mapper.KeyMapper.mapKeys(KeyMapper.java:108)
	at org.jboss.aesh.edit.mapper.KeyMapper.mapQuoteKeys(KeyMapper.java:49)
	at org.jboss.aesh.console.Config.parseInputrc(Config.java:127)
	at org.jboss.aesh.console.Console.reset(Console.java:150)
	at org.jboss.aesh.console.Console.<init>(Console.java:105)
	at org.jboss.aesh.console.Console.<init>(Console.java:101)
	at org.jboss.as.cli.impl.Console$Factory.getConsole(Console.java:85)
	at org.jboss.as.cli.impl.Console$Factory.getConsole(Console.java:78)
	at org.jboss.as.cli.impl.CommandContextImpl.initBasicConsole(CommandContextImpl.java:349)
	at org.jboss.as.cli.impl.CommandContextImpl.<init>(CommandContextImpl.java:296)
	at org.jboss.as.cli.impl.CommandContextFactoryImpl.newCommandContext(CommandContextFactoryImpl.java:76)
	at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:273)
	at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:253)
	at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.modules.Module.run(Module.java:312)
	at org.jboss.modules.Main.main(Main.java:460)

Expectation is that CLI should not have terminated suddenly rather the exception should have been handled in a proper way.

Assignee:: Alexey Loubyansky

Reporter:: Jay SenSharma (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2015/03/20 2:18 AM

Updated:: 2021/10/24 6:15 AM

Resolved:: 2015/05/13 5:02 PM

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates