[JBoss JIRA] (DROOLS-4576) Data object selector Search widget not enabled in saved tests
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4576?page=com.atlassian.jira.plug... ]
Yeser Amer edited comment on DROOLS-4576 at 1/16/20 9:26 AM:
-------------------------------------------------------------
Tech comments: Basically, the search should be enabled not only when an empty column is selected. It should store the inserted key during grid switch.
DROOLS-4823
was (Author: yamer):
Tech comments: Basically, the search should be enabled not only when an empty column is selected. It should store the inserted key during grid switch.
> Data object selector Search widget not enabled in saved tests
> -------------------------------------------------------------
>
> Key: DROOLS-4576
> URL: https://issues.redhat.com/browse/DROOLS-4576
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: 2019-09-27 13.36.19.gif
>
>
> The Search widget doesn't work (isn't accessible/enabled) in a test template that has been setup/saved, it does work in a new test though. Example attached.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4576) Data object selector Search widget not enabled in saved tests
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-4576?page=com.atlassian.jira.plug... ]
Yeser Amer commented on DROOLS-4576:
------------------------------------
Tech comments: Basically, the search should be enabled not only when an empty column is selected. It should store the inserted key during grid switch.
> Data object selector Search widget not enabled in saved tests
> -------------------------------------------------------------
>
> Key: DROOLS-4576
> URL: https://issues.redhat.com/browse/DROOLS-4576
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: 2019-09-27 13.36.19.gif
>
>
> The Search widget doesn't work (isn't accessible/enabled) in a test template that has been setup/saved, it does work in a new test though. Example attached.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (SWSQE-1052) Uninstallation of istio leaves cluster in broken state
by Filip Brychta (Jira)
[ https://issues.redhat.com/browse/SWSQE-1052?page=com.atlassian.jira.plugi... ]
Filip Brychta resolved SWSQE-1052.
----------------------------------
Resolution: Done
Caused by https://github.com/istio/istio/issues/20238
Added workaround
> Uninstallation of istio leaves cluster in broken state
> ------------------------------------------------------
>
> Key: SWSQE-1052
> URL: https://issues.redhat.com/browse/SWSQE-1052
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> When the upstream istio is removed from cluster it leaves the cluster in broken state.
> New pods fail to start with:
> (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_registry-puller-89bd55495-8qc6s_registry-puller_b0cf5e01-383d-11ea-93d2-fa163ee5acb3_0(d93218e9cc51c4a6ed1a49829e9983d01ba0071bea5bb55dfadbac9345aa3996): Multus: Err adding pod to network "k8s-pod-network": Multus: error in invoke Conflist add - "k8s-pod-network": error in getting result from AddNetworkList: failed to find plugin "istio-cni" in path [/var/lib/cni/bin /opt/multus/bin]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12982) MP fault tolerance: CDI contexts not available in @Timeout methods
by Ladislav Thon (Jira)
[ https://issues.redhat.com/browse/WFLY-12982?page=com.atlassian.jira.plugi... ]
Ladislav Thon commented on WFLY-12982:
--------------------------------------
Indeed the new implementation should address this.
> MP fault tolerance: CDI contexts not available in @Timeout methods
> ------------------------------------------------------------------
>
> Key: WFLY-12982
> URL: https://issues.redhat.com/browse/WFLY-12982
> Project: WildFly
> Issue Type: Bug
> Components: MP Fault Tolerance
> Affects Versions: 19.0.0.Beta1
> Reporter: Miroslav Novak
> Assignee: Radoslav Husar
> Priority: Major
>
> Say I have a {{@Timeout}} method in my application, which uses a {{@RequestScoped}} service:
> {code:java}
> @Inject
> private MyService service;
> @Timeout
> public String doSomething() throws InterruptedException {
> return "Hello " + service.call();
> }
> {code}
> The method isn't {{@Asynchronous}}, so it's supposed to be executed on the caller thread and hence the CDI contexts should be available. However, they are not:
> {code}
> 2018-04-03 21:16:35,976 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
> {code}
> Clearly the {{@Timeout}} methods are always executed on a separate thread (see {{HystrixCommandInterceptor.initSetter}}):
> {code:java}
> // Async and timeout operations use THREAD isolation strategy
> if (operation.isAsync() || operation.hasTimeout()) {
> propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.THREAD);
> } else {
> propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.SEMAPHORE);
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12982) MP fault tolerance: CDI contexts not available in @Timeout methods
by Miroslav Novak (Jira)
[ https://issues.redhat.com/browse/WFLY-12982?page=com.atlassian.jira.plugi... ]
Miroslav Novak commented on WFLY-12982:
---------------------------------------
This is known issue THORN-1930 with MP FT. Cloning to WFLY as with new MP FT implementation this might be solved.
> MP fault tolerance: CDI contexts not available in @Timeout methods
> ------------------------------------------------------------------
>
> Key: WFLY-12982
> URL: https://issues.redhat.com/browse/WFLY-12982
> Project: WildFly
> Issue Type: Bug
> Components: MP Fault Tolerance
> Affects Versions: 19.0.0.Beta1
> Reporter: Miroslav Novak
> Assignee: Radoslav Husar
> Priority: Major
>
> Say I have a {{@Timeout}} method in my application, which uses a {{@RequestScoped}} service:
> {code:java}
> @Inject
> private MyService service;
> @Timeout
> public String doSomething() throws InterruptedException {
> return "Hello " + service.call();
> }
> {code}
> The method isn't {{@Asynchronous}}, so it's supposed to be executed on the caller thread and hence the CDI contexts should be available. However, they are not:
> {code}
> 2018-04-03 21:16:35,976 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
> {code}
> Clearly the {{@Timeout}} methods are always executed on a separate thread (see {{HystrixCommandInterceptor.initSetter}}):
> {code:java}
> // Async and timeout operations use THREAD isolation strategy
> if (operation.isAsync() || operation.hasTimeout()) {
> propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.THREAD);
> } else {
> propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.SEMAPHORE);
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (WFLY-12982) MP fault tolerance: CDI contexts not available in @Timeout methods
by Miroslav Novak (Jira)
Miroslav Novak created WFLY-12982:
-------------------------------------
Summary: MP fault tolerance: CDI contexts not available in @Timeout methods
Key: WFLY-12982
URL: https://issues.redhat.com/browse/WFLY-12982
Project: WildFly
Issue Type: Bug
Components: MP Fault Tolerance
Affects Versions: 19.0.0.Beta1
Reporter: Miroslav Novak
Assignee: Radoslav Husar
Say I have a {{@Timeout}} method in my application, which uses a {{@RequestScoped}} service:
{code:java}
@Inject
private MyService service;
@Timeout
public String doSomething() throws InterruptedException {
return "Hello " + service.call();
}
{code}
The method isn't {{@Asynchronous}}, so it's supposed to be executed on the caller thread and hence the CDI contexts should be available. However, they are not:
{code}
2018-04-03 21:16:35,976 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped
{code}
Clearly the {{@Timeout}} methods are always executed on a separate thread (see {{HystrixCommandInterceptor.initSetter}}):
{code:java}
// Async and timeout operations use THREAD isolation strategy
if (operation.isAsync() || operation.hasTimeout()) {
propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.THREAD);
} else {
propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.SEMAPHORE);
}
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months