December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-280) Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-280?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-280: ---------------------------------------- The pull request has been reviewed and merged, I think the original concern reported here is now resolved as the majority of the messages are logged at a low enough level to avoid the desire for logging IDs. I will still continue to look at contributing IDs for the remainder but I think that is certainly in the nice to have category now. > Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID > ---------------------------------------------------------------------- > > Key: WFWIP-280 > URL: https://issues.redhat.com/browse/WFWIP-280 > Project: WildFly WIP > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Critical > > Warning which are propagated to log from io.smallrye.jwt.auth package don't have assigned logging ID. > Example: > {code} > 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4799) Adding "expression" type handling for Collection type propereties

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4799?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4799: ------------------------------------------- [~jomarko] I agree that we should just save the picked option. But could we recap what's happening when the switch from one radio option to the other? I'm confused about where we left things. *User case: User enters options using one radio selection (define/create) then switches to another radio selection.* We maintain the values in both options (Create/Define), but only Save the one that's visible /selected. - Anything entered in the other selection clears out at Save. - We don't notify the user at save about "losing" the alternate option values that were being maintained. - We don't try to convert values from expression to form-based. Is that correct? > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4799 > URL: https://issues.redhat.com/browse/DROOLS-4799 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-11-26 at 1.26.54 PM.png, dmn-dt-enumeration-constraint.png, dmn-dt-expression-constraint.png, expression-list_error.png, scesim-list.png > > > I need a clarification regarding the behaviour of the updated Collection Editor, in particular for this section -->https://marvelapp.com/5ab248j/screen/62093042/layer/102496330. > Considering the editor introduces a new way to handle a Collection ("Define List"), can you please give us detailed behaviour for the following case: > - What happen if a user starts to input data inside a section (Define List/Create List) and then switch on the other one? > eg. if I start to define a List using "Define List" option (i.e. an expression) and then I change to "Create List" case. What should happen? > - Currently, after adding a Collection, the Grid cell will show "List (1)". It should be the same for "Define list" (i.e. Expression) case? > In case of additional clarificaiton, I'll update this ticket. > Hope it's clear, if not you can contact me anytime. > Thanks -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12650) EL does not handle identifiers as JavaBeans

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12650?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-12650: --------------------------------- Labels: downstream_dependency (was: ) > EL does not handle identifiers as JavaBeans > ------------------------------------------- > > Key: WFLY-12650 > URL: https://issues.redhat.com/browse/WFLY-12650 > Project: WildFly > Issue Type: Bug > Components: EE, Web (Undertow) > Affects Versions: 18.0.0.Final > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > Labels: downstream_dependency > Fix For: 19.0.0.Beta1 > > Attachments: ELTest.war > > > Even if defined JavaBeans using <jsp:useBean> in jsp, the EL expression is handled as java Class if that class is already imported in jsp. > {code:title=EX)test1.jsp|borderStyle=solid} > <%@ page language="java" contentType="text/html; charset=UTF-8" pageEncoding="UTF-8"%> > <%@page import="test.TestMBean"%> > <html> > <head> > <title>Test1</title> > </head> > <body> > <jsp:useBean id="TestMBean" class="test.TestMBean"/> > TestMBean.test : ${TestMBean.test} <br/> > </body> > </html> > {code} > Therefore, the following exceptions may occur: > {noformat} > Caused by: javax.el.PropertyNotFoundException: Either 'test' is not a public static field of the class 'test.TestMBean' or field is inacessable > at javax.el.StaticFieldELResolver.getValue(StaticFieldELResolver.java:107) > at org.apache.jasper.el.JasperELResolver.getValue(JasperELResolver.java:110) > at com.sun.el.parser.AstValue.getValue(AstValue.java:139) > at com.sun.el.parser.AstValue.getValue(AstValue.java:203) > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:226) > at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:917) > at org.apache.jsp.test1_jsp._jspService(test1_jsp.java:107) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:433) > ... 46 more > {noformat} > According [EL spec|https://download.oracle.com/otn-pub/jcp/el-3_0-fr-eval-spec/EL3.0.FR...], Evaluating of the imported static field should be the last. > {quote} > 1.5.1 Evaluating Identifiers > The steps are used for evaluating an identifier. > ■ If the identifier is a lambda argument passed to a lambda expression invocation, its value is returned. > ■ Else if the identifier is a variable, the associated expression is evaluated and returned. > ■ Else if the identifier is resolved by the ELResolvers, the value returned from the ELResolvers is returned. > ■ Else if the identifier is an imported static field, its value is returned. > ■ Else return not resolved. > One implication of the explicit search order of the identifiers is that an identifier hides other identifiers (of the same name) that come after it in the list. > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4681) [DMN Designer] Data Types - Implement the new dropdown design in the type selector

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4681?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4681: ------------------------------------ Story Points: 5 > [DMN Designer] Data Types - Implement the new dropdown design in the type selector > ---------------------------------------------------------------------------------- > > Key: DROOLS-4681 > URL: https://issues.redhat.com/browse/DROOLS-4681 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: prototype.png > > > Implement the new dropdown design in the type selector, following the prototype: > !prototype.png|width=600! > Notice: this JIRA comprehends the tooltip into the label as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4681) [DMN Designer] Data Types - Implement the new dropdown design in the type selector

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4681?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4681: ------------------------------------ Sprint: 2019 Week 50-52 (from Dec 9) > [DMN Designer] Data Types - Implement the new dropdown design in the type selector > ---------------------------------------------------------------------------------- > > Key: DROOLS-4681 > URL: https://issues.redhat.com/browse/DROOLS-4681 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: prototype.png > > > Implement the new dropdown design in the type selector, following the prototype: > !prototype.png|width=600! > Notice: this JIRA comprehends the tooltip into the label as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-280) Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-280?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-280: ---------------------------------------- Reviewing the code within SmallRye JWT the primary issue that I actually see is not the content of the error messages i.e. the lack of ID but the level and verbosity of the messages. Under normal operation a server should expect to handle both valid and invalid tokens, although an invalid token is an error it is still normal and so should not result in per request logging so I have raised the following PR to see if they will accept lowering the log levels: - https://github.com/smallrye/smallrye-jwt/pull/156 As a third party project they can reject some / all of these proposed changes. A short term back up could be to turn off SmallRye JWT logging in our default configuration, longer term something that could be interesting to discuss is if internally we could re-map the levels for specific categories. > Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID > ---------------------------------------------------------------------- > > Key: WFWIP-280 > URL: https://issues.redhat.com/browse/WFWIP-280 > Project: WildFly WIP > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Darran Lofthouse > Priority: Critical > > Warning which are propagated to log from io.smallrye.jwt.auth package don't have assigned logging ID. > Example: > {code} > 11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism] (default task-1) Unable to validate bearer token: Failed to verify token: io.smallrye.jwt.auth.principal.ParseException: Failed to verify token > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4485) [DMN Designer] Data Types - Add visual indication for showing the current drag level

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4485?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4485: ------------------------------------ Sprint: 2019 Week 50-52 (from Dec 9) > [DMN Designer] Data Types - Add visual indication for showing the current drag level > ------------------------------------------------------------------------------------ > > Key: DROOLS-4485 > URL: https://issues.redhat.com/browse/DROOLS-4485 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: image-2019-08-27-12-40-51-854.png > > > Show a visual indication of the current drag level. See (the blue line): > !image-2019-08-27-12-40-51-854.png|width=500! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4866) ActivationsSorter: Comparison method violates its general contract!

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4866?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4866. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/951fcd311a48d51f23d4553c1b64bb7... > ActivationsSorter: Comparison method violates its general contract! > ------------------------------------------------------------------- > > Key: DROOLS-4866 > URL: https://issues.redhat.com/browse/DROOLS-4866 > Project: Drools > Issue Type: Bug > Affects Versions: 7.30.0.Final > Environment: - JDK 1.8.0_181 (64 bit) > Reporter: Leonid Sotnikov > Assignee: Mario Fusco > Priority: Major > Attachments: sorttest.zip > > > Hi. > While serializing a session with ProtobufOutputMarshaller we've encountered an exception in a few rare cases when the activations are sorted by {{Collections.sort( dormant, ActivationsSorter.INSTANCE )}}: > {code} > Caused by: java.lang.IllegalArgumentException: Comparison method violates its general contract! > at java.util.TimSort.mergeHi(TimSort.java:899) > at java.util.TimSort.mergeAt(TimSort.java:516) > at java.util.TimSort.mergeForceCollapse(TimSort.java:457) > at java.util.TimSort.sort(TimSort.java:254) > at java.util.Arrays.sort(Arrays.java:1512) > at java.util.ArrayList.sort(ArrayList.java:1462) > at java.util.Collections.sort(Collections.java:175) > (...) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1039) Fix publish_jenkins_console.py

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1039: ------------------------------------ Summary: Fix publish_jenkins_console.py Key: SWSQE-1039 URL: https://issues.redhat.com/browse/SWSQE-1039 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Job Filter pattern: "[\w-]+ #\d+" Output Filter pattern: "" Jenkins Version: 2.190.2 OrderedDict([('python-ui-test-pr', set([472])), ('upstream-pipeline', set([544])), ('build-kiali', set([871])), ('install-maistra', set([1377])), ('clean-environment', set([3240, 3241, 3242, 3239])), ('istio-kiali-mesh-checker', set([1864, 1865, 1866])), ('install-bookinfo', set([1619, 1620])), ('install-kiali-test-mesh-operator', set([881])), ('run-kiali-ui-tests-parallel', set([454])), ('run-kiali-ui-tests', set([7630, 7631, 7632, 7633, 7634, 7635, 7636, 7637, 7638, 7639, 7640, 7641, 7642, 7643, 7644, 7645, 7646]))]) {'run-kiali-ui-tests-parallel': 'UNSTABLE', 'python-ui-test-pr': 'UNSTABLE', 'build-kiali': 'SUCCESS', 'istio-kiali-mesh-checker': 'SUCCESS', 'upstream-pipeline': 'UNSTABLE', 'clean-environment': 'SUCCESS', 'run-kiali-ui-tests': 'UNSTABLE', 'install-bookinfo': 'SUCCESS', 'install-maistra': 'SUCCESS', 'install-kiali-test-mesh-operator': 'SUCCESS'} Traceback (most recent call last): File "publish_jenkins_console.py", line 150, in <module> _url = _upload_console_log(_name, _ids_list) File "publish_jenkins_console.py", line 126, in _upload_console_log _url = _response.json()['url'] File "/usr/lib/python2.7/site-packages/requests/models.py", line 897, in json return complexjson.loads(self.text, **kwargs) File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads return _default_decoder.decode(s) File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode raise ValueError("No JSON object could be decoded") ValueError: No JSON object could be decoded cat: /home/jenkins/agent/workspace/python-ui-test-pr/build_comment_log.md: No such file or directory -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1035) Wizard - TLS MUTUAL

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1035?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1035: ---------------------------------- Sprint: Kiali Sprint #30 > Wizard - TLS MUTUAL > ------------------- > > Key: SWSQE-1035 > URL: https://issues.redhat.com/browse/SWSQE-1035 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > > Client Certificate > Private Key -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019