June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5384) Clicking rightmost column's header in DMN decision table raises an error

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5384?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-5384: ------------------------------------------- Fix Version/s: 7.40.0.Final (was: 7.39.0.Final) > Clicking rightmost column's header in DMN decision table raises an error > ------------------------------------------------------------------------ > > Key: DROOLS-5384 > URL: https://issues.redhat.com/browse/DROOLS-5384 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Fix For: 7.40.0.Final > > Attachments: dmn-decision-table-error-popup-7.38.0.png, drools5384.mp4 > > > When I import Traffic_Violation sample, opened a "Fine" decision table. The rightmost column's header is empty ("Enter Text") and I get an error pop-up when clicked. (At the first time, it raises an error popup. After that, the header is unresponsive) > See screenshot. > Chrome 80.0.3987.122 > Firefox 60.6.2 > h3. Acceptance criteria > - DMN grids are not affected > - GDST grid is unaffected > - Scesim grid is unaffected -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5291) Import of empty scesim file leads to Unexpected error

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5291?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-5291: ------------------------------------------- Fix Version/s: 7.40.0.Final (was: 7.39.0.Final) > Import of empty scesim file leads to Unexpected error > ----------------------------------------------------- > > Key: DROOLS-5291 > URL: https://issues.redhat.com/browse/DROOLS-5291 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.36.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools, kogito-tooling > Fix For: 7.40.0.Final > > Attachments: Traffic.zip, errorlog.txt, image-2020-04-17-16-47-29-261.png, image-2020-04-17-16-47-32-047.png > > > If user generate a scesim file using vs code extention it is not comparable with BC. > Use Vscode generated files [^Traffic.zip] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5230) Managing a List of structures in Test Scenario editor produces an Exception

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5230?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-5230: ------------------------------------------- Fix Version/s: 7.40.0.Final (was: 7.39.0.Final) > Managing a List of structures in Test Scenario editor produces an Exception > --------------------------------------------------------------------------- > > Key: DROOLS-5230 > URL: https://issues.redhat.com/browse/DROOLS-5230 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.34.0.Final > Reporter: Tracy Hires > Assignee: Yeser Amer > Priority: Critical > Fix For: 7.40.0.Final > > Attachments: Error screen shot.png, test_scenario_list_exception.zip > > > When trying to delete an item from a list of structures with nested structures in the scenario editor, an exception is thrown with a message that is not helpful to the end user. > Log entry is: > ``` > ^[[0m^[[31m17:16:51,564 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-415) Error from user: xxxxx Error ID: -881202734 Location: LibraryPerspective|$ProjectScreen[!Worg.kie.dmn.decision.navigator,EDiagramEditorPropertiesScreen,Eorg.drools.scenariosimulation.TestTools?scesimeditorid=1,!Eorg.drools.scenariosimulation.TestTools?scesimeditorid=2,Eorg.docks.PlaceHolder?name=testRunnerReportingPanel,Worg.kie.guvnor.explorer,],DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Math%2520Functions.dmn&file_name=Math%20Functions.dmn&has_version_support=true,DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Divide.dmn&file_name=Divide.dmn&has_version_support=true,org.kie.workbench.common.screens.messageconsole.MessageConsole,,AddAssetsScreen,ScenarioSimulationEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/test/resources/Test%2520Math%2520Functions.scesim&file_name=Test%20Math%20Functions.scesim&has_version_support=true Exception: Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined > ``` > From UI I could see: `Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined` > (Screenshot is attached) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5223) User cannot open malformed scesim file. Loading popup is spining infinitive times

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5223?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-5223: ------------------------------------------- Fix Version/s: 7.40.0.Final (was: 7.39.0.Final) > User cannot open malformed scesim file. Loading popup is spining infinitive times > --------------------------------------------------------------------------------- > > Key: DROOLS-5223 > URL: https://issues.redhat.com/browse/DROOLS-5223 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.33.0.Final, 7.34.0.Final, 7.35.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Fix For: 7.40.0.Final > > Attachments: Traffic.scesim > > > If user import Scesim file that have xml tag unclosed, > then user gets warning, but loading popup is not disappearing > and user cannot proceed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5394) Coverage Report Improvements (CVS File)

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5394?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-5394: ------------------------------------------- Fix Version/s: 7.40.0.Final (was: 7.39.0.Final) > Coverage Report Improvements (CVS File) > --------------------------------------- > > Key: DROOLS-5394 > URL: https://issues.redhat.com/browse/DROOLS-5394 > Project: Drools > Issue Type: Enhancement > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Fix For: 7.40.0.Final > > > Proposed solution tohttps://issues.redhat.com/browse/RHPAM-2616, is to put the same data shown on Coverage Report inside the generated CSV Report file. > This means to add following data: > Overall Stats (Available rules, executed rules, coverage percentage); > Rules counters -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-322) [EAP7-1337] Allow users to setup a source clone secrets manually

by Petr Kremensky (Jira)

[ https://issues.redhat.com/browse/WFWIP-322?page=com.atlassian.jira.plugin... ] Petr Kremensky updated WFWIP-322: --------------------------------- Description: Source clone secrets are used to provide the builder Pod with access it would not normally have access to, such as private repositories or repositories with self-signed or untrusted SSL certificates. We should add {{sourceSecret}} field into SourceRepositorySpec API in order to allow users to manually add a clone secret to their setup. See https://docs.openshift.com/container-platform/4.4/builds/creating-build-i... for more details on the source secret functionality. Users could use the {{source-secret-match-uri}} method to link sourceSecret automatically, but I think we should allow them to use {{sourceSecret}} as well to provide support both options how to solve this. was: Source clone secrets are used to provide the builder Pod with access it would not normally have access to, such as private repositories or repositories with self-signed or untrusted SSL certificates. We should add {{sourceSecret}} field into SourceRepositorySpec API in order to allow users to manually add a clone secret to their setup. See https://docs.openshift.com/container-platform/4.4/builds/creating-build-i... for more details on the source secret functionality. Users could use the {{source-secret-match-uri}} method to link sourceSecret automatically, but I think we should allow them to use {{sourceSecret}} as well to provide a full support for this. > [EAP7-1337] Allow users to setup a source clone secrets manually > ---------------------------------------------------------------- > > Key: WFWIP-322 > URL: https://issues.redhat.com/browse/WFWIP-322 > Project: WildFly WIP > Issue Type: Quality Risk > Components: OpenShift > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Major > > Source clone secrets are used to provide the builder Pod with access it would not normally have access to, such as private repositories or repositories with self-signed or untrusted SSL certificates. We should add {{sourceSecret}} field into SourceRepositorySpec API in order to allow users to manually add a clone secret to their setup. See https://docs.openshift.com/container-platform/4.4/builds/creating-build-i... for more details on the source secret functionality. > > Users could use the {{source-secret-match-uri}} method to link sourceSecret automatically, but I think we should allow them to use {{sourceSecret}} as well to provide support both options how to solve this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13234) WF17 vs. WF18: org.infinispan.hibernate-cache

by Daniel Wehrle (Jira)

[ https://issues.redhat.com/browse/WFLY-13234?page=com.atlassian.jira.plugi... ] Daniel Wehrle commented on WFLY-13234: -------------------------------------- Hi Scott, any news on this? Regards, Daniel > WF17 vs. WF18: org.infinispan.hibernate-cache > --------------------------------------------- > > Key: WFLY-13234 > URL: https://issues.redhat.com/browse/WFLY-13234 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Affects Versions: 18.0.1.Final > Reporter: Daniel Wehrle > Assignee: Scott Marlow > Priority: Major > > Hi. > Why has the entity cache transaction in org.infinispan.hibernate-cache been changed from NON_XA to NONE (default) and what are the implications? Can this lead to performance problems? > WF17 > {code} > <cache-container name="hibernate" module="org.infinispan.hibernate-cache"> > <local-cache name="entity"> > <transaction mode="NON_XA"/> > <object-memory size="10000"/> > <expiration max-idle="100000"/> > </local-cache> > {code} > WF18 > {code} > <cache-container name="hibernate" module="org.infinispan.hibernate-cache"> > <local-cache name="entity"> > <object-memory size="10000"/> > <expiration max-idle="100000"/> > </local-cache> > {code} > Best regards, > Daniel -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-322) [EAP7-1337] Allow users to setup a source clone secrets manually

by Petr Kremensky (Jira)

Petr Kremensky created WFWIP-322: ------------------------------------ Summary: [EAP7-1337] Allow users to setup a source clone secrets manually Key: WFWIP-322 URL: https://issues.redhat.com/browse/WFWIP-322 Project: WildFly WIP Issue Type: Quality Risk Components: OpenShift Reporter: Petr Kremensky Assignee: Jeff Mesnil Source clone secrets are used to provide the builder Pod with access it would not normally have access to, such as private repositories or repositories with self-signed or untrusted SSL certificates. We should add {{sourceSecret}} field into SourceRepositorySpec API in order to allow users to manually add a clone secret to their setup. See https://docs.openshift.com/container-platform/4.4/builds/creating-build-i... for more details on the source secret functionality. Users could use the {{source-secret-match-uri}} method to link sourceSecret automatically, but I think we should allow them to use {{sourceSecret}} as well to provide a full support for this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5006) Improve readability of domain host controller server logs in tests

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFCORE-5006?page=com.atlassian.jira.plug... ] Richard Achmatowicz reassigned WFCORE-5006: ------------------------------------------- Assignee: Richard Achmatowicz > Improve readability of domain host controller server logs in tests > ------------------------------------------------------------------ > > Key: WFCORE-5006 > URL: https://issues.redhat.com/browse/WFCORE-5006 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 12.0.1.Final > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 13.0.0.Beta1 > > > When domain tests involve multiple DCs and HCs starting on the same server, its difficult to differentiate between output from different host controllers. > At a minimum, associating the configuration host name with host controller startup and started messages would help in the readability of server logs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5006) Improve readability of domain host controller server logs in tests

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFCORE-5006?page=com.atlassian.jira.plug... ] Richard Achmatowicz updated WFCORE-5006: ---------------------------------------- Summary: Improve readability of domain host controller server logs in tests (was: Improve readability of domain host controller server logs) > Improve readability of domain host controller server logs in tests > ------------------------------------------------------------------ > > Key: WFCORE-5006 > URL: https://issues.redhat.com/browse/WFCORE-5006 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 12.0.1.Final > Reporter: Richard Achmatowicz > Priority: Major > Fix For: 13.0.0.Beta1 > > > When domain tests involve multiple DCs and HCs starting on the same server, its difficult to differentiate between output from different host controllers. > At a minimum, associating the configuration host name with host controller startup and started messages would help in the readability of server logs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 June 2020