January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1505) org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1505?page=com.atlassian.jira.plugin.s... ] Jan Kalina edited comment on ELY-1505 at 1/29/18 11:25 AM: ----------------------------------------------------------- [~istudens] I am testing against *Oracle-jdk-8u161* (from Oracle's tar.gz) on Fedora 27 and the test succeed. How has you achieved it? {code} JAVA_HOME=/opt/Oracle-jdk-8u161 PATH=/opt/Oracle-jdk-8u161/bin/:$PATH mvn test -Dtest=org.wildfly.security.asn1.DEREncoderTest {code} {code} [INFO] Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.212 s - in org.wildfly.security.asn1.DEREncoderTest {code} was (Author: honza889): [~istudens] I am testing against *Oracle-jdk-8u161* (from Oracle's tar.gz) on Fedora 27 and the test succeed. How has you achieved it? > org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161 > ---------------------------------------------------------------- > > Key: ELY-1505 > URL: https://issues.jboss.org/browse/ELY-1505 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Reporter: Ivo Studensky > Assignee: Jan Kalina > Priority: Minor > > The org.wildfly.security.asn1.DEREncoderTest#testEncodeDSAKey() fails on JDK8 v.161 due to: > {noformat} > [ERROR] testEncodeDSAKey(org.wildfly.security.asn1.DEREncoderTest) Time elapsed: 0.124 s <<< ERROR! > java.security.InvalidKeyException: The security strength of SHA-1 digest algorithm is not sufficient for this key size > at sun.security.provider.DSA.checkKey(DSA.java:111) > at sun.security.provider.DSA.engineInitSign(DSA.java:143) > at java.security.Signature$Delegate.init(Signature.java:1156) > at java.security.Signature$Delegate.chooseProvider(Signature.java:1116) > at java.security.Signature$Delegate.engineInitSign(Signature.java:1180) > at java.security.Signature.initSign(Signature.java:531) > at org.wildfly.security.asn1.DEREncoderTest.testEncodeDSAKey(DEREncoderTest.java:458) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > {noformat} > It affects also older tags, not only 1.1.8. It might be related to > https://bugs.java.com/view_bug.do?bug_id=8184341 > It seems to be a testsuite issue only. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1505) org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1505?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1505: --------------------------------- [~istudens] I am testing against *Oracle-jdk-8u161* (from Oracle's tar.gz) on Fedora 27 and the test succeed. How has you achieved it? > org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161 > ---------------------------------------------------------------- > > Key: ELY-1505 > URL: https://issues.jboss.org/browse/ELY-1505 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Reporter: Ivo Studensky > Assignee: Jan Kalina > Priority: Minor > > The org.wildfly.security.asn1.DEREncoderTest#testEncodeDSAKey() fails on JDK8 v.161 due to: > {noformat} > [ERROR] testEncodeDSAKey(org.wildfly.security.asn1.DEREncoderTest) Time elapsed: 0.124 s <<< ERROR! > java.security.InvalidKeyException: The security strength of SHA-1 digest algorithm is not sufficient for this key size > at sun.security.provider.DSA.checkKey(DSA.java:111) > at sun.security.provider.DSA.engineInitSign(DSA.java:143) > at java.security.Signature$Delegate.init(Signature.java:1156) > at java.security.Signature$Delegate.chooseProvider(Signature.java:1116) > at java.security.Signature$Delegate.engineInitSign(Signature.java:1180) > at java.security.Signature.initSign(Signature.java:531) > at org.wildfly.security.asn1.DEREncoderTest.testEncodeDSAKey(DEREncoderTest.java:458) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > {noformat} > It affects also older tags, not only 1.1.8. It might be related to > https://bugs.java.com/view_bug.do?bug_id=8184341 > It seems to be a testsuite issue only. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2273) [DMN Editor] Contextual selection - Hover state

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2273?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2273: ----------------------------------- Sprint: 2018 Week 03-04, 2018 Week 05-06 (was: 2018 Week 03-04) > [DMN Editor] Contextual selection - Hover state > ----------------------------------------------- > > Key: DROOLS-2273 > URL: https://issues.jboss.org/browse/DROOLS-2273 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Elements within a logic table that offer contextual actions will present a hover state on focus. Examples of elements that might offer actions include: Rows, cells, columns, table… Or in context terms: Rules, Inputs/Outputs, Context row, etc -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2214) [DMN Editor] Content of the decision node is not copied

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2214?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2214: ----------------------------------- Sprint: 2018 Week 03-04, 2018 Week 05-06 (was: 2018 Week 03-04) > [DMN Editor] Content of the decision node is not copied > ------------------------------------------------------- > > Key: DROOLS-2214 > URL: https://issues.jboss.org/browse/DROOLS-2214 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: Stunner > > User has possibility to copy a DRG node by a CTRL+C shortcut, however the problem is that content of the node is not copied. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2217) [DMN Editor] Allow DMN persistence for an incomplete, still being authored, DMN model

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2217?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2217: ----------------------------------- Sprint: 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2018 Week 01-02, 2018 Week 03-04) > [DMN Editor] Allow DMN persistence for an incomplete, still being authored, DMN model > ------------------------------------------------------------------------------------- > > Key: DROOLS-2217 > URL: https://issues.jboss.org/browse/DROOLS-2217 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Attachments: Screenshot from 2018-01-22 14-01-38.png, Screenshot from 2018-01-22 14-02-13.png, error.log > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2109) [XLS Decision Table] New Asset Dialogue misses descriptions

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2109?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2109: ----------------------------------- Sprint: 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > [XLS Decision Table] New Asset Dialogue misses descriptions > ----------------------------------------------------------- > > Key: DROOLS-2109 > URL: https://issues.jboss.org/browse/DROOLS-2109 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Optional > Attachments: Screenshot from 2017-11-03 10-20-21.png > > > The attached dialogue shows missing descriptions for table format and file selector. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1795) [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1795?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1795: ----------------------------------- Sprint: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column. > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1795 > URL: https://issues.jboss.org/browse/DROOLS-1795 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Final > Reporter: Mark Coble > Assignee: Mark Coble > Priority: Minor > Fix For: 7.0.0.Final > > Attachments: guvnor-3507.png > > > If a condition BRL column is added to a DT with bound variables that are used in an action column and that variable name is subsequently changed, the attached error message occurs when updating the action column with the new variable name. In the attached message the original variable name is 'app'. Hitting 'ok' returns you to the DT which has actually refactored the DT with the new variable name and validation is successful. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1701) FEEL code generation and compilation

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1701?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1701: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > FEEL code generation and compilation > ------------------------------------ > > Key: DROOLS-1701 > URL: https://issues.jboss.org/browse/DROOLS-1701 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1825: ----------------------------------- Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Labels: UX > Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png, GDTAnalysis(a)2x.png, GDTColumns(a)2x.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1609) Augment FEEL AST node at compilation with return type

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1609?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1609: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04) > Augment FEEL AST node at compilation with return type > ----------------------------------------------------- > > Key: DROOLS-1609 > URL: https://issues.jboss.org/browse/DROOLS-1609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > This is needed so to be able to determine the result of a boxed function at compile time, in turn to be able at compile time to determine a valid compilation without error of a BKM for instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2018