June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3904) NPE at TAB completion

by Erich Duda (JIRA)

Erich Duda created WFCORE-3904: ---------------------------------- Summary: NPE at TAB completion Key: WFCORE-3904 URL: https://issues.jboss.org/browse/WFCORE-3904 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 5.0.0.Final Reporter: Erich Duda Assignee: Jean-Francois Denise Priority: Blocker When you write some command into the CLI prompt (without enter), move cursor to beginning of line and hit TAB, the CLI crashes on {{NullPointerException}}. {code} [standalone@localhost:9990 /] /system-property=x:read-resource read-resource read-resource-description Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.NullPointerException at org.jboss.as.cli.impl.aesh.cmd.operation.OperationCommandContainer.isOperation(OperationCommandContainer.java:53) at org.jboss.as.cli.impl.aesh.CLICommandRegistry.getCommand(CLICommandRegistry.java:258) at org.jboss.as.cli.impl.aesh.CLICommandRegistry.isLegacyCommand(CLICommandRegistry.java:343) at org.jboss.as.cli.impl.aesh.CLICompletionHandler.complete(CLICompletionHandler.java:134) at org.jboss.as.cli.impl.CLICommandCompleter.doComplete(CLICommandCompleter.java:132) at org.jboss.as.cli.impl.CLICommandCompleter.complete(CLICommandCompleter.java:54) at org.jboss.as.cli.impl.aesh.CLICompletionHandler.complete(CLICompletionHandler.java:69) at org.jboss.as.cli.impl.aesh.CLICompletionHandler.complete(CLICompletionHandler.java:45) at org.aesh.readline.completion.CompletionHandler.createCompletionList(CompletionHandler.java:134) at org.aesh.readline.completion.CompletionHandler.complete(CompletionHandler.java:102) at org.aesh.readline.action.mappings.Complete.accept(Complete.java:62) at org.aesh.readline.Readline$AeshInputProcessor.parse(Readline.java:245) at org.aesh.readline.Readline$AeshInputProcessor.access$100(Readline.java:174) at org.aesh.readline.Readline.readInput(Readline.java:95) at org.aesh.readline.Readline.access$1000(Readline.java:57) at org.aesh.readline.Readline$AeshInputProcessor.lambda$start$1(Readline.java:333) at org.aesh.terminal.EventDecoder.accept(EventDecoder.java:118) at org.aesh.terminal.EventDecoder.accept(EventDecoder.java:31) at org.aesh.io.Decoder.write(Decoder.java:133) at org.aesh.readline.tty.terminal.TerminalConnection.openBlocking(TerminalConnection.java:212) at org.aesh.readline.tty.terminal.TerminalConnection.openBlocking(TerminalConnection.java:199) at org.jboss.as.cli.impl.ReadlineConsole$CLITerminalConnection.lambda$null$1(ReadlineConsole.java:171) at java.lang.Thread.run(Thread.java:748) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2271) Race condition in BaseServer.getConnection

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2271?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2271: --------------------------- Fix Version/s: 4.0.12 3.6.16 > Race condition in BaseServer.getConnection > ------------------------------------------ > > Key: JGRP-2271 > URL: https://issues.jboss.org/browse/JGRP-2271 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.10 > Reporter: Dennis Reed > Assignee: Bela Ban > Fix For: 4.0.12, 3.6.16 > > > BaseServer.getConnection creates a socket and puts it in the shared map under a lock. > However it does not connect the socket inside the lock, so another thread calling getConnection at the same time can get the unconnected socket, which will throw a NPE when used because it's not connected yet (all the checks before returning and using it only look for isOpen, not isConnected). > java.lang.NullPointerException > at org.jgroups.blocks.cs.TcpConnection.doSend(TcpConnection.java:184) > at org.jgroups.blocks.cs.TcpConnection._send(TcpConnection.java:171) > at org.jgroups.blocks.cs.TcpConnection.send(TcpConnection.java:141) > at org.jgroups.blocks.cs.BaseServer.send(BaseServer.java:185) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2551) Executable model - tests from package "integrationtests.operators" fail when run with executable model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2551?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2551: ------------------------------------- 5th fix https://github.com/kiegroup/drools/commit/a9661836bf8c122b683e3d2cddd96a9... > Executable model - tests from package "integrationtests.operators" fail when run with executable model > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-2551 > URL: https://issues.jboss.org/browse/DROOLS-2551 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Luca Molteni > > When running tests from package org.drools.compiler.integrationtests.operators [1] with executable model, many of them fail (~120 out of ~520). To run the tests with the model, I moved the tests to a separate module in this PR [2], please check the PR description to see how to run them. > [1] https://github.com/kiegroup/drools/tree/d7ad4fb31647b5295c3cbc0321f0d8f89... > [2] https://github.com/kiegroup/drools/pull/1901 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2551) Executable model - tests from package "integrationtests.operators" fail when run with executable model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2551?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2551. --------------------------------- Resolution: Done > Executable model - tests from package "integrationtests.operators" fail when run with executable model > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-2551 > URL: https://issues.jboss.org/browse/DROOLS-2551 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Luca Molteni > > When running tests from package org.drools.compiler.integrationtests.operators [1] with executable model, many of them fail (~120 out of ~520). To run the tests with the model, I moved the tests to a separate module in this PR [2], please check the PR description to see how to run them. > [1] https://github.com/kiegroup/drools/tree/d7ad4fb31647b5295c3cbc0321f0d8f89... > [2] https://github.com/kiegroup/drools/pull/1901 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2575) Executable model - DRL integration tests fail with the model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2575?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2575: ------------------------------------- First test cases fixed by https://github.com/kiegroup/drools/commit/b2f0e50eff5dd45a3963ecd20fb28e8... > Executable model - DRL integration tests fail with the model > ------------------------------------------------------------ > > Key: DROOLS-2575 > URL: https://issues.jboss.org/browse/DROOLS-2575 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > When running DRL integration tests [1] with the executable model, 118 out of 510 test cases fail. PR with tests is here [2]. > [1] https://github.com/kiegroup/drools/tree/master/drools-compiler/src/test/j... > [2] https://github.com/kiegroup/drools/pull/1915 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2610) Add support for Guice AOP features like BindInterceptors

by Tmob Fami (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2610?page=com.atlassian.jira.plugi... ] Tmob Fami updated DROOLS-2610: ------------------------------ Attachment: guice-4.0-no_aop.jar > Add support for Guice AOP features like BindInterceptors > -------------------------------------------------------- > > Key: DROOLS-2610 > URL: https://issues.jboss.org/browse/DROOLS-2610 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.4.1.Final > Reporter: Tmob Fami > Assignee: Mario Fusco > Labels: downstream_dependency > Attachments: guice-4.0-no_aop.jar > > > 7.4.1.final is missing support for GoogleGuice AOP versionsm I noticed it brings guice-4.0-no_aop. This is causing a dependency conflict with GoogleGuice 4.0 (we have a direct dependency on it for interceptors module). Drools's guice takes precedence at binding time takes, causing compile and runtime issues. > Can you please consider adding AOP support? This is a showstopper for us at the moment, will force to look at alternative solutions, which is not ideal given Drool's amazing runtime capabilities > i was also wondering what's the rationale behind the decision in the first place? Do you have any recommendations to suppressDrools Guice? Looking forward to the response -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2610) Add support for Guice AOP features like BindInterceptors

by Tmob Fami (JIRA)

Tmob Fami created DROOLS-2610: --------------------------------- Summary: Add support for Guice AOP features like BindInterceptors Key: DROOLS-2610 URL: https://issues.jboss.org/browse/DROOLS-2610 Project: Drools Issue Type: Feature Request Components: core engine Affects Versions: 7.4.1.Final Reporter: Tmob Fami Assignee: Mario Fusco (7.4.1.Final) for our rules processing needs. I hit a roadblock and was wondering if you could provide pointers on resolving that. 7.4.1.final is missing support for GoogleGuice AOP versionsm I noticed it brings guice-4.0-no_aop. This is causing a dependency conflict with GoogleGuice 4.0 (we have a direct dependency on it for interceptors module). Drools's guice takes precedence at binding time takes, causing compile and runtime issues. Can you please consider adding AOP support? This is a showstopper for us at the moment, will force to look at alternative solutions, which is not ideal given Drool's amazing runtime capabilities i was also wondering what's the rationale behind the decision in the first place? Do you have any recommendations to suppressDrools Guice? Looking forward to the response -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2610) Add support for Guice AOP features like BindInterceptors

by Tmob Fami (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2610?page=com.atlassian.jira.plugi... ] Tmob Fami updated DROOLS-2610: ------------------------------ Description: 7.4.1.final is missing support for GoogleGuice AOP versionsm I noticed it brings guice-4.0-no_aop. This is causing a dependency conflict with GoogleGuice 4.0 (we have a direct dependency on it for interceptors module). Drools's guice takes precedence at binding time takes, causing compile and runtime issues. Can you please consider adding AOP support? This is a showstopper for us at the moment, will force to look at alternative solutions, which is not ideal given Drool's amazing runtime capabilities i was also wondering what's the rationale behind the decision in the first place? Do you have any recommendations to suppressDrools Guice? Looking forward to the response was: (7.4.1.Final) for our rules processing needs. I hit a roadblock and was wondering if you could provide pointers on resolving that. 7.4.1.final is missing support for GoogleGuice AOP versionsm I noticed it brings guice-4.0-no_aop. This is causing a dependency conflict with GoogleGuice 4.0 (we have a direct dependency on it for interceptors module). Drools's guice takes precedence at binding time takes, causing compile and runtime issues. Can you please consider adding AOP support? This is a showstopper for us at the moment, will force to look at alternative solutions, which is not ideal given Drool's amazing runtime capabilities i was also wondering what's the rationale behind the decision in the first place? Do you have any recommendations to suppressDrools Guice? Looking forward to the response > Add support for Guice AOP features like BindInterceptors > -------------------------------------------------------- > > Key: DROOLS-2610 > URL: https://issues.jboss.org/browse/DROOLS-2610 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.4.1.Final > Reporter: Tmob Fami > Assignee: Mario Fusco > Labels: downstream_dependency > > 7.4.1.final is missing support for GoogleGuice AOP versionsm I noticed it brings guice-4.0-no_aop. This is causing a dependency conflict with GoogleGuice 4.0 (we have a direct dependency on it for interceptors module). Drools's guice takes precedence at binding time takes, causing compile and runtime issues. > Can you please consider adding AOP support? This is a showstopper for us at the moment, will force to look at alternative solutions, which is not ideal given Drool's amazing runtime capabilities > i was also wondering what's the rationale behind the decision in the first place? Do you have any recommendations to suppressDrools Guice? Looking forward to the response -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2532: ------------------------------------- [~uxdlc] Thanks for clarification and updated wireframes. I like this idea about highlighting cells where expectations were not fulfilled. > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: RoundF.pdf, roundE-scaled.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-42) Pushing of n key should cause searching of last pattern from history

by Erich Duda (JIRA)

Erich Duda created WFWIP-42: ------------------------------- Summary: Pushing of n key should cause searching of last pattern from history Key: WFWIP-42 URL: https://issues.jboss.org/browse/WFWIP-42 Project: WildFly WIP Issue Type: Enhancement Reporter: Erich Duda Assignee: Jean-Francois Denise When you open file by {{less}} or {{vim}} and as a first command you push {{n}} key, the applications start to search last pattern from the history. I would expect the same behavior in CLI. Note: I know that history of patterns is not persisted in CLI. However it is persisted between commands in one session. E.g. I can dump elytron subsystem and search an attribute, then dump messaging subsystem and search the same attribute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2018