Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-608

Using ? as control character in .inputrc causes CLI to terminate immediately.

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.0.0.CR4, 2.0.0.Alpha1
    • None
    • CLI
    • None

      • 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.

            [WFCORE-608] Using ? as control character in .inputrc causes CLI to terminate immediately.

            Petr Penicka <ppenicka@redhat.com> changed the Status of bug 1203997 from VERIFIED to CLOSED

            RH Bugzilla Integration added a comment - Petr Penicka <ppenicka@redhat.com> changed the Status of bug 1203997 from VERIFIED to CLOSED

            Marek Kopecky <mkopecky@redhat.com> changed the Status of bug 1203997 from ON_QA to VERIFIED

            RH Bugzilla Integration added a comment - Marek Kopecky <mkopecky@redhat.com> changed the Status of bug 1203997 from ON_QA to VERIFIED

            Vladimir Dosoudil <dosoudil@redhat.com> changed the Status of bug 1203997 from MODIFIED to ON_QA

            RH Bugzilla Integration added a comment - Vladimir Dosoudil <dosoudil@redhat.com> changed the Status of bug 1203997 from MODIFIED to ON_QA

            baranowb <bbaranow@redhat.com> changed the Status of bug 1203997 from ASSIGNED to MODIFIED

            RH Bugzilla Integration added a comment - baranowb <bbaranow@redhat.com> changed the Status of bug 1203997 from ASSIGNED to MODIFIED

            olubyans@redhat.com Please reschedule this to either 1.0.0.CR4 or 2.something. Thanks.

            Brian Stansberry added a comment - olubyans@redhat.com Please reschedule this to either 1.0.0.CR4 or 2.something. Thanks.

            baranowb <bbaranow@redhat.com> changed the Status of bug 1203997 from NEW to ASSIGNED

            RH Bugzilla Integration added a comment - baranowb <bbaranow@redhat.com> changed the Status of bug 1203997 from NEW to ASSIGNED

            The cli is now catching RuntimeException's from Aesh during the console initialization. And the next release of Aesh will not throw RuntimeException in this case.

            Alexey Loubyansky added a comment - The cli is now catching RuntimeException's from Aesh during the console initialization. And the next release of Aesh will not throw RuntimeException in this case.

              olubyans@redhat.com Alexey Loubyansky
              jaysensharma Jay SenSharma (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: