[JBoss JIRA] (WFCORE-1684) Empty lines between tab completion suggestions on Windows
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1684?page=com.atlassian.jira.plugi... ]
Petr Kremensky moved JBEAP-5478 to WFCORE-1684:
-----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1684 (was: JBEAP-5478)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Affects Version/s: (was: 7.1.0.DR1)
> Empty lines between tab completion suggestions on Windows
> ---------------------------------------------------------
>
> Key: WFCORE-1684
> URL: https://issues.jboss.org/browse/WFCORE-1684
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Petr Kremensky
> Assignee: Alexey Loubyansky
> Priority: Minor
>
> I noticed that CLI put empty lines between lines with suggested values once the Windows terminal is set to maximal width. Issue appears *only of the CLI is connected to the EAP running in domain* mode.
> *reproduce*
> \- start EAP in domain mode
> \- open a new terminal window, manually set the terminal width to maximal allowed value, but do not maximize the window
> \- connect CLI to the running server and pres the Tab key
> {noformat}
> [domain@localhost:9990 /]
> : clear data-source echo if pwd reload shutdown unset
> alias command deploy echo-dmr jdbc-driver-info quit rollout-plan try version
> batch connect deployment-info help ls read-attribute run-batch unalias xa-data-source
> cd connection-info deployment-overlay history patch read-operation set undeploy
> {noformat}
> I was able to reproduce the issue on W2K8 and W2K12 servers.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (DROOLS-747) declared window, type length(1), do actually contain more than 1 object (with reteoo)
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-747?page=com.atlassian.jira.plugin... ]
Mario Fusco closed DROOLS-747.
------------------------------
Resolution: Out of Date
> declared window, type length(1), do actually contain more than 1 object (with reteoo)
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-747
> URL: https://issues.jboss.org/browse/DROOLS-747
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Attachments: 20150323.DROOLS-747-reproducer.zip
>
>
> h5. Premise
> I know reteoo is progressively being deprecated, but I think until is there is helpful for A/B testing of possible leaks comparing with phreak (like it happened during 610Final) so reporting this bug.
> h5. Executive summary
> Declaring a window of type length (1) should always contain 1 object.
> h5. Details
> With reference to attached reproducer.
> Given the following knowledge base:
> {code}
> global java.util.concurrent.atomic.AtomicLong globalCounter;
> declare Measurement
> @role(event)
> end
> declare window lastMeasurement
> Measurement() over window:length( 1 ) // from entry-point DEFAULT
> end
> rule "IFF the last Measurement that I know of, is of ID color, increment the counter"
> no-loop
> when
> Measurement( id == "color" ) from window lastMeasurement
> then
> globalCounter.incrementAndGet();
> end
> {code}
> The goal is: IFF the last Measurement that I know of, is of ID "color", increment the counter. Please notice you ought to separate the window being just on Measurement, in order to know the last Measurement regardless of the ID, and then you have a rule acting on the declared window, to check IFF this last Measurement, is actually of ID "color".
> Now assuming you just have created the session and the following increment/insert/fire:
> {code}
> AtomicLong globalCounter = new AtomicLong(0);
> session.setGlobal("globalCounter", globalCounter);
> session.fireAllRules();
> assertEquals("no data, still 0", 0, globalCounter.get());
> LOG.info("Now running data");
> clock.advanceTime(1, TimeUnit.MINUTES);
> Measurement mRed= new Measurement("color", "red");
> session.insert(mRed);
> Measurement mGreen= new Measurement("color", "green");
> session.insert(mGreen);
> Measurement mBlue= new Measurement("color", "blue");
> session.insert(mBlue);
> session.fireAllRules();
> LOG.info("Final checks");
> assertEquals("win lenght =1 was: ", 1, globalCounter.get());
> {code}
> At the end you should have the global counter with value = 1, because we inserted 3 events of type Measurement, but the declared window lastMeasurement should reference only {{mBlue}}, which should be later picked by the rule because the ID is "color", and increment the counter by 1.
> This works with phreak, it does not work with reteo.
> phreak globalCounter = 1 : OK
> reteoo globalCounter = 3 : FAIL.
> Could you kindly advise, please?
> Thanks
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFCORE-1683) Home and End keys doesn't work on Windows
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1683?page=com.atlassian.jira.plugi... ]
Petr Kremensky updated WFCORE-1683:
-----------------------------------
Description:
Home and End keys doesn't work properly on Windows.
*actual*
{noformat}
[disconnected /] echo<HOME> test
[disconnected /] echoαG[] test
[disconnected /] echo<END> test
[disconnected /] echoαO[] test
{noformat}
*expected*
{noformat}
[disconnected /] echo<HOME> test
[disconnected /] []echo test
[disconnected /] echo<END> test
[disconnected /] echo test[]
{noformat}
was:
Home and End keys doesn't work properly on Windows.
*actual*
{noformat}
[disconnected /] echo<HOME> test
[disconnected /] echoαG test
[disconnected /] echo<END> test
[disconnected /] echoαO test
{noformat}
*expected*
{noformat}
[disconnected /] echo<HOME> test
[disconnected /] []echo test
[disconnected /] echo<END> test
[disconnected /] echo test[]
{noformat}
> Home and End keys doesn't work on Windows
> -----------------------------------------
>
> Key: WFCORE-1683
> URL: https://issues.jboss.org/browse/WFCORE-1683
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Petr Kremensky
> Assignee: Alexey Loubyansky
>
> Home and End keys doesn't work properly on Windows.
> *actual*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] echoαG[] test
> [disconnected /] echo<END> test
> [disconnected /] echoαO[] test
> {noformat}
> *expected*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] []echo test
> [disconnected /] echo<END> test
> [disconnected /] echo test[]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFCORE-1683) Home and End keys doesn't work on Windows
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1683?page=com.atlassian.jira.plugi... ]
Petr Kremensky moved JBEAP-5476 to WFCORE-1683:
-----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1683 (was: JBEAP-5476)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Affects Version/s: (was: 7.1.0.DR1)
Affects Testing: (was: Regression)
> Home and End keys doesn't work on Windows
> -----------------------------------------
>
> Key: WFCORE-1683
> URL: https://issues.jboss.org/browse/WFCORE-1683
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Petr Kremensky
> Assignee: Alexey Loubyansky
>
> Home and End keys doesn't work properly on Windows.
> *actual*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] echoαG test
> [disconnected /] echo<END> test
> [disconnected /] echoαO test
> {noformat}
> *expected*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] []echo test
> [disconnected /] echo<END> test
> [disconnected /] echo test[]
> {noformat}
> The issues is a regression against EAP 6.4.0
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFCORE-1683) Home and End keys doesn't work on Windows
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1683?page=com.atlassian.jira.plugi... ]
Petr Kremensky updated WFCORE-1683:
-----------------------------------
Description:
Home and End keys doesn't work properly on Windows.
*actual*
{noformat}
[disconnected /] echo<HOME> test
[disconnected /] echoαG test
[disconnected /] echo<END> test
[disconnected /] echoαO test
{noformat}
*expected*
{noformat}
[disconnected /] echo<HOME> test
[disconnected /] []echo test
[disconnected /] echo<END> test
[disconnected /] echo test[]
{noformat}
was:
Home and End keys doesn't work properly on Windows.
*actual*
{noformat}
[disconnected /] echo<HOME> test
[disconnected /] echoαG test
[disconnected /] echo<END> test
[disconnected /] echoαO test
{noformat}
*expected*
{noformat}
[disconnected /] echo<HOME> test
[disconnected /] []echo test
[disconnected /] echo<END> test
[disconnected /] echo test[]
{noformat}
The issues is a regression against EAP 6.4.0
> Home and End keys doesn't work on Windows
> -----------------------------------------
>
> Key: WFCORE-1683
> URL: https://issues.jboss.org/browse/WFCORE-1683
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Petr Kremensky
> Assignee: Alexey Loubyansky
>
> Home and End keys doesn't work properly on Windows.
> *actual*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] echoαG test
> [disconnected /] echo<END> test
> [disconnected /] echoαO test
> {noformat}
> *expected*
> {noformat}
> [disconnected /] echo<HOME> test
> [disconnected /] []echo test
> [disconnected /] echo<END> test
> [disconnected /] echo test[]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-6898) ConcurrentModificationException when returning from JMS onMessage() MBean
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/WFLY-6898?page=com.atlassian.jira.plugin.... ]
Tomas Remes commented on WFLY-6898:
-----------------------------------
Hi [~traivor]
Do you have some reproducer please?
> ConcurrentModificationException when returning from JMS onMessage() MBean
> -------------------------------------------------------------------------
>
> Key: WFLY-6898
> URL: https://issues.jboss.org/browse/WFLY-6898
> Project: WildFly
> Issue Type: Feature Request
> Components: CDI / Weld
> Affects Versions: 10.1.0.CR1
> Reporter: Harold Campbell
> Assignee: Stuart Douglas
>
> I receive the following stacktrace when an MBean's onMessage() returns. The transaction is rolled back and the message marked as undelivered. This started sometime after nightly #2280 which works fine for me.
> 2016-07-30 21:51:49,273 TRACE [com.envestnet.ejb.winthorpe.optimizer.WinthorpeRunListener] (Thread-0 (ActiveMQ-client-global-threads-556320704)) Finished processing run 16819
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:159)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:256)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:329)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:239)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)
> at com.envestnet.ejb.winthorpe.optimizer.WinthorpeRunListener$$$view3.onMessage(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139)
> at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73)
> at com.envestnet.ejb.winthorpe.optimizer.WinthorpeRunListener$$$endpoint1.onMessage(Unknown Source)
> at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:310)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1018)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:48)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1145)
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:103)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429)
> at java.util.HashMap$KeyIterator.next(HashMap.java:1453)
> at org.jboss.weld.context.AbstractContext.destroy(AbstractContext.java:160)
> at org.jboss.weld.context.AbstractManagedContext.deactivate(AbstractManagedContext.java:58)
> at org.jboss.weld.context.AbstractBoundContext.deactivate(AbstractBoundContext.java:72)
> at org.jboss.weld.context.ejb.EjbRequestContextImpl.deactivate(EjbRequestContextImpl.java:47)
> at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:76)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (DROOLS-1223) java.lang.NullPointerException druing Condition Evaluation
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1223?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-1223.
---------------------------------
Resolution: Cannot Reproduce Bug
I have no idea how to reproduce your issue and I'm almost sure that it is caused by a null value in your domain objects. If you can provide a reproducer feel free to attach it here and reopen this ticket.
> java.lang.NullPointerException druing Condition Evaluation
> ----------------------------------------------------------
>
> Key: DROOLS-1223
> URL: https://issues.jboss.org/browse/DROOLS-1223
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.3.0.Final, 6.4.0.Final
> Reporter: Rodrigo Doria Medina
> Assignee: Mario Fusco
>
> {panel:title=Code}
> Caused by: java.lang.NullPointerException
> at ConditionEvaluator2afa7f52e3ae42c98bf357b4d12bd2f2.evaluate(Unknown Source)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:214)
> at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:146)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> at org.drools.core.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:359)
> at org.drools.core.reteoo.EntryPointNode.propagateModify(EntryPointNode.java:249)
> at org.drools.core.phreak.PropagationEntry$Update.execute(PropagationEntry.java:150)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:78)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:68)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2011)
> at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278)
> {panel}
> This happens when running more than once the same piece of data. (It happens from the second time).
> I have no clue what could that be. When running the first time everything computes as expected.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFCORE-1682) Missleading tab completion for edit-batch-line command
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1682?page=com.atlassian.jira.plugi... ]
Petr Kremensky moved JBEAP-5474 to WFCORE-1682:
-----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1682 (was: JBEAP-5474)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Affects Version/s: (was: 7.1.0.DR1)
Affects Testing: (was: Regression)
> Missleading tab completion for edit-batch-line command
> ------------------------------------------------------
>
> Key: WFCORE-1682
> URL: https://issues.jboss.org/browse/WFCORE-1682
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Petr Kremensky
> Assignee: Alexey Loubyansky
>
> Tab completion for edit-batch-list command suggest to use --line-number as a command option, but that is not how the command works.
> *command usage*
> {noformat}
> [standalone@localhost:9990 /] batch
> [standalone@localhost:9990 / #] :read-resource
> [standalone@localhost:9990 / #] list-batch
> #1 /:read-resource
> [standalone@localhost:9990 / #] edit-batch-line 1 :read-attribute(name=launch-type)
> #1 :read-attribute(name=launch-type)
> [standalone@localhost:9990 / #] list-batch
> #1 :read-attribute(name=launch-type)
> {noformat}
> *actual*
> {noformat}
> [standalone@localhost:9990 / #] edit-batch-line <TAB>
> [standalone@localhost:9990 / #] edit-batch-line --<TAB>
> --help --line-number
> [standalone@localhost:9990 / #] edit-batch-line --line-number=1 :read-attribute(name=launch-type)
> Failed to parse line number '--line-number=1': For input string: "--line-number=1"
> {noformat}
> {{--line-number}} shouldn't be offered by tab completion for the command.
> Misleading tab completion ends up with syntax error.
> *expected*
> {noformat}
> [standalone@localhost:9990 / #] edit-batch-line <TAB>
> --help
> {noformat}
> The issue is a regression against EAP 7.0.0 release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months