January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2417) Ref-counting for messages

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2417?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2417: --------------------------- Fix Version/s: 5.1 (was: 5.0) > Ref-counting for messages > ------------------------- > > Key: JGRP-2417 > URL: https://issues.redhat.com/browse/JGRP-2417 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.1 > > > When users do their own memory management, the message passed to {{Channel.send()}} might have a reference to a memory area that's allocated from a pool, and that needs to be returned when done. > However, the return of a {{Channel.send()}} call does not necessarily mean that the memory area can be reused. If, for example, NAKACK2 or UNICAST3 have the message in their retransmission tables (to potentially retransmit it), then the memory cannot be reused until that message has been purged from the retransmission table. > Add a reference-counting mechanism to {{Message}} (implemented in {{BaseMessage}}) that allows NAKACK2 or UNICAST3 to increment a ref-count. When a message is purged from the retransmission table, decrement its ref-count. When the ref-count is 0, a callback could be called. The callback could for example return the associated memory chunk back to the memory pool. > This could possibly be a trait, with a no-op implementation as default. This could be overwritten, ie. > {code:java} > Message release() { > if(refcount <= 0) > // give associated memory area back to pool > } > {code} > See if this needs to be integrated with {{MessageFactory}} as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4132) Pure Client Side Scenario Simulation Editor

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4132?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4132: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Pure Client Side Scenario Simulation Editor > ------------------------------------------- > > Key: DROOLS-4132 > URL: https://issues.redhat.com/browse/DROOLS-4132 > Project: Drools > Issue Type: Epic > Reporter: Eder Ignatowicz > Assignee: Yeser Amer > Priority: Major > > The goal of this phase: Be able to have a pure client-side editor for Scenario Simulation. > The end result of this epic will be a client-side distribution of Scenario Simulation working on VSCode and able to run and show the result of the test execution. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Sunil Kondkar (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Sunil Kondkar commented on SWSQE-1048: -------------------------------------- Not able to create Meshpolicy in the example below: https://kiali.io/documentation/validations/#_meshpolicy_enabling_mtls_fou... I can create ServiceMeshpolicy by changing apiVersion and kind to below values: apiVersion: "authentication.maistra.io/v1" kind: "ServiceMeshPolicy" > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4136) R&D how to run scenario simulation tests inside VSCode

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4136?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4136: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > R&D how to run scenario simulation tests inside VSCode > ------------------------------------------------------ > > Key: DROOLS-4136 > URL: https://issues.redhat.com/browse/DROOLS-4136 > Project: Drools > Issue Type: Task > Reporter: Eder Ignatowicz > Assignee: Yeser Amer > Priority: Major > > The main goal of this JIRA is to research what are the best approaches in order to run scenario simulation tests inside VSCode client-side only distribution. > Eder's first ideas: > [1] Run kie-server inside a docker image and run scenario tests via REST API > [2] Show the result of test execution inside scenario simulation editor > <add your idea here> > On future: [1] + investigate if it's possible to show tests execution results inside another junit vscode extension -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4134) Create a scenario simulation distribution

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4134?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-4134. ------------------------------------ Release Notes Text: Covered by https://issues.redhat.com/browse/DROOLS-3879 Resolution: Duplicate Issue > Create a scenario simulation distribution > ----------------------------------------- > > Key: DROOLS-4134 > URL: https://issues.redhat.com/browse/DROOLS-4134 > Project: Drools > Issue Type: Task > Reporter: Eder Ignatowicz > Assignee: Gabriele Cardosi > Priority: Major > > Create a scenario simulation client-side editor based on our base showcase. This editor will only be able to do a simple POC inside VSCode. For now, we will have a mocked marshaller and we will not run/execute any test scenario. Moreover, also the base data used to create the scenario simulation (DMOs/DMNs) will be hardcoded > The end result of this JIRA is a scenario simulation editor visible inside VSCode with mocked data. > This war should be manually included inside the current VSCode extension. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4135) Scenario Simulation Marshaller

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4135?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-4135. ------------------------------------ Release Notes Text: Covered by https://issues.redhat.com/browse/DROOLS-4249 Resolution: Duplicate Issue > Scenario Simulation Marshaller > ------------------------------ > > Key: DROOLS-4135 > URL: https://issues.redhat.com/browse/DROOLS-4135 > Project: Drools > Issue Type: Task > Reporter: Eder Ignatowicz > Assignee: Gabriele Cardosi > Priority: Major > > <TODO after Marshaller BAPL> -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4133) Extract and Refactor Scenario Simulation Modules

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4133?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-4133. ------------------------------------ Release Notes Text: Covered by https://issues.redhat.com/browse/DROOLS-3879 Resolution: Duplicate Issue > Extract and Refactor Scenario Simulation Modules > ------------------------------------------------ > > Key: DROOLS-4133 > URL: https://issues.redhat.com/browse/DROOLS-4133 > Project: Drools > Issue Type: Task > Reporter: Eder Ignatowicz > Assignee: Gabriele Cardosi > Priority: Major > > In order to be ready to be used on business central and kogito, scenario simulation codebase should be split into three modules: > Client Core (environment-agnostic implementations and interfaces) > Business central module (depends on Client Core) > Kogito module (depends on Client Core) > Business central scenario simulation distribution will be made by bc + core and kogito distribution by kogito + core -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4145) R&D how to import/export CSV inside VSCode

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4145?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-4145. ------------------------------------ Release Notes Text: Import/Exprto of CSV inside SCESIM should be managed by scesim itself, not delegated to the container Resolution: Won't Do > R&D how to import/export CSV inside VSCode > ------------------------------------------ > > Key: DROOLS-4145 > URL: https://issues.redhat.com/browse/DROOLS-4145 > Project: Drools > Issue Type: Enhancement > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3439) Prevent selection of specific cells in Scenario Simulation

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-3439?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-3439: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Prevent selection of specific cells in Scenario Simulation > ---------------------------------------------------------- > > Key: DROOLS-3439 > URL: https://issues.redhat.com/browse/DROOLS-3439 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Optional > Labels: drools-tools > Attachments: table.png > > > It would improve the user experience if some of the cells could not be selected at all; specifically cells #, Scenario description, GIVEN, EXPECT, and row numbers, as it should not be possible to change them anyway. > This follows up keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4726) Bound facts from model are available on Background

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4726?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4726: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Bound facts from model are available on Background > -------------------------------------------------- > > Key: DROOLS-4726 > URL: https://issues.redhat.com/browse/DROOLS-4726 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bound-facts-on-background.webm > > > See the attached video. The bound facts from main model tab are available in the Background tab. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

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 January 2020