January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4903) In constraints fail to compile if negated or inside a forall pattern

by Matteo Casalino (Jira)

Matteo Casalino created DROOLS-4903: --------------------------------------- Summary: In constraints fail to compile if negated or inside a forall pattern Key: DROOLS-4903 URL: https://issues.redhat.com/browse/DROOLS-4903 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.31.0.Final Reporter: Matteo Casalino Assignee: Mario Fusco Attachments: in-constraint-negation.tgz It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-291) Log messages from io.smallrye.openapi don't have message ID

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFWIP-291?page=com.atlassian.jira.plugin... ] Paul Ferraro closed WFWIP-291. ------------------------------ Resolution: Rejected WildFly has no such requirement that debug or trace messages use i18n (and thus have a message ID). > Log messages from io.smallrye.openapi don't have message ID > ----------------------------------------------------------- > > Key: WFWIP-291 > URL: https://issues.redhat.com/browse/WFWIP-291 > Project: WildFly WIP > Issue Type: Bug > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Major > > Messages logged by io.smallrye.openapi don't have assigned ID: > {code} > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.util.SchemaFactory] (MSC service thread 1-4) Processing a single @Schema annotation. > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing a single @Response annotation. > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing jax-rs method: {0} > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiDataObjectScanner] (MSC service thread 1-4) Starting processing with root: java.lang.String > {code} > A search in SmallRye implementation seems to show that IDs are not used even when level is WARN: > {code} > $ find . -name '*.*' -type f -print0 | xargs -0 grep --color -n -e 'LOG.warn' > ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:551: LOG.warnf("Matrix parameter references missing path segment: %s", segmentName); > ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:1147: LOG.warnf("Value '%s' is not a valid %s default", stringValue, primitive.name().toLowerCase()); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2429) MsgStats num_bytes_sent should be incremented by the Message::size

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2429?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2429: -------------------------------- [~dan.berindei] You're right > MsgStats num_bytes_sent should be incremented by the Message::size > ------------------------------------------------------------------ > > Key: JGRP-2429 > URL: https://issues.redhat.com/browse/JGRP-2429 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.8 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > Fix For: 4.1.9 > > > MsgStats num_bytes_sent should be incremented by the Message::size > Today it is incremented by the Message:length that is the length of the payload, it doesn't include the headers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

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

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1048: --------------------------------------- "More than one Destination Rule for the same host subset combination" error text before was a different one. > 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)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4788) Upgrade org.apache.httpcomponents:httpclient 4.5.10

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4788?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4788: -------------------------------- Component/s: Server (was: Test Suite) > Upgrade org.apache.httpcomponents:httpclient 4.5.10 > --------------------------------------------------- > > Key: WFCORE-4788 > URL: https://issues.redhat.com/browse/WFCORE-4788 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Affects Versions: 11.0.0.Beta5 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4788) Upgrade org.apache.httpcomponents:httpclient 4.5.10

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4788: ----------------------------------- Summary: Upgrade org.apache.httpcomponents:httpclient 4.5.10 Key: WFCORE-4788 URL: https://issues.redhat.com/browse/WFCORE-4788 Project: WildFly Core Issue Type: Component Upgrade Components: Test Suite Affects Versions: 11.0.0.Beta5 Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12486) Memory leak in OpenTracing when deployment is redeployed multiple times

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-12486?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-12486: ------------------------------------------ https://github.com/wildfly/wildfly/pull/12878 if https://github.com/wildfly/wildfly/pull/12836 doesn't make it to feature freeze. > Memory leak in OpenTracing when deployment is redeployed multiple times > ----------------------------------------------------------------------- > > Key: WFLY-12486 > URL: https://issues.redhat.com/browse/WFLY-12486 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 17.0.0.Final, 17.0.1.Final, 18.0.1.Final > Reporter: Jan Stourac > Assignee: Emmanuel Hugonnet > Priority: Blocker > Attachments: memory-leak-bad.png, memory-leak-good.png, wildfly-thread-leak.png > > > There seems to be a memory leak when a deployment is redeployed multiple times (100 times in our test). This is very similar to what has been described in WFLY-10991. Also first commit this started to happen is [this one|https://github.com/wildfly/wildfly/commit/74170b5f49dd83f6b9ebd489f85...] - JaegerTracing and Apache Thrift dependencies update. Thus I selected MP OpenTracing component for this issue. > Test and deployment is same as is described in WFLY-10991. > Size of the extra heap in use is about 27MB plus when compared to the initial size before multiple redeploy operations. > I've tried to check manually via [visualVM|https://visualvm.github.io/] tool. Screenshot with suspicious jaegertracing instances are attached - there are much more jaegertracing class instances with new version of Jager Tracing and Apache Thrift dependencies, which is suspicious. > Interesting thing is that when microprofile-opentracing-smallrye subsystem is removed via: > {code} > /subsystem=microprofile-opentracing-smallrye:remove() > {code} > the memory leak is still present. This is kind of confusing to me. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4787) Fix or disable failing tests on IBM JDK

by Peter Mackay (Jira)

Peter Mackay created WFCORE-4787: ------------------------------------ Summary: Fix or disable failing tests on IBM JDK Key: WFCORE-4787 URL: https://issues.redhat.com/browse/WFCORE-4787 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: Peter Mackay Assignee: Richard Opalka Fix For: 10.0.0.Beta3, 10.0.0.Final The following tests are failing on latest IBM JDK 8: --- # testsuite/standalone SilentModeTestCase # testsuite/manualmode CLIEmbedHostControllerTestCase CLIEmbedServerTestCase --- Tested on: --- java version "1.8.0_211" Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled) OpenJ9 - 46e57f9 OMR - 06a046a IBM - 0b909bf) JCL - 20190409_01 based on Oracle jdk8u211-b25 --- -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4786) Upgrade Jandex 2.1.2.Final

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4786: ----------------------------------- Summary: Upgrade Jandex 2.1.2.Final Key: WFCORE-4786 URL: https://issues.redhat.com/browse/WFCORE-4786 Project: WildFly Core Issue Type: Component Upgrade Components: Server Affects Versions: 11.0.0.Beta5 Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3048) [DMN Designer] CellEditorControl needs to issue a new instance per use

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-3048?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-3048: -------------------------------- Attachment: applicationscope-vs-dependendscope.webm > [DMN Designer] CellEditorControl needs to issue a new instance per use > ---------------------------------------------------------------------- > > Key: DROOLS-3048 > URL: https://issues.redhat.com/browse/DROOLS-3048 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: applicationscope-vs-dependendscope.webm > > > A {{Popover}} used to edit a cell or column header (or any other DOM-based editor for that matter) disappears following a change in the widget that causes a {{Layer.draw()}} if the grid is sufficiently wide that there is a column not visible on screen. > All cells/columns that use {{CellEditorControls}} (containing, for example, the {{Popover}}) share a single instance from {{CellEditorControl}} and hence although the User makes a change in a visible column the invisible column (scrolled off screen) has its DOM resources destroyed that is the same instance as that for the visible column. > See https://github.com/kiegroup/appformer/blob/master/uberfire-extensions/ube.... If a column is not in the _body_ or _floating_ columns collection its DOM resources are destroyed. > I probably need to ensure different instances of {{CellEditorControl}} are created for each column/cell where we currently share the same instance. Also check for destruction of DOM elements in {{Document}} when grids/columns etc are destroyed. > h3. Acceptance criteria > # Create a DMN model > # Add a Decision > # Set its expression to a Decision Table > # Add multiple Input and Output columns so that the table is wider than the visible screen space (i.e. some columns are not rendered) > # Click on the header of a visible column > # The Name/Data-type popup should appear > # Repeat for expression type of Relation -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2020