February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3567) Import tab, with cards.

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3567?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3567: ------------------------------------- * Well, I think the contextual menu on the tree might be iffy/unusual and am wondering if dragging would be more do-able and intuitive, wdyt?[~manstis] [~tirelli] * Wrt contextual menus in the canvas, I got the idea that was possible. * As far as creating DRDs and using imported components, don't we need that? > Import tab, with cards. > ----------------------- > > Key: DROOLS-3567 > URL: https://issues.jboss.org/browse/DROOLS-3567 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UXTeam, drools-tools > Attachments: Import-tab.pdf > > > Detail Import design as presented in: https://issues.jboss.org/browse/DROOLS-2999 > Specify any details not already covered by the patternfly card pattern: https://www.patternfly.org/pattern-library/content-views/card-view/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3567) Import tab, with cards.

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3567?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3567: ---------------------------------------- Hi [~uxdlc] it wasn't the Card View that concerned me. It was the (nice) context menus and whole "click through" of importing, using imported items and creating a DRD that impressed me most... and something we have absolutely no implementation of yet.. I am half-joking when I say I hope we can make it as nice :-) > Import tab, with cards. > ----------------------- > > Key: DROOLS-3567 > URL: https://issues.jboss.org/browse/DROOLS-3567 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UXTeam, drools-tools > Attachments: Import-tab.pdf > > > Detail Import design as presented in: https://issues.jboss.org/browse/DROOLS-2999 > Specify any details not already covered by the patternfly card pattern: https://www.patternfly.org/pattern-library/content-views/card-view/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-526) UI Tests - Make version compatible to run for TP

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-526?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-526: -------------------------------------- Please also change 'swagger_address' in 'conf/env.yaml' file when tagging. It should refer to appropriate kiali tagged version's swagger. > UI Tests - Make version compatible to run for TP > ------------------------------------------------ > > Key: SWSQE-526 > URL: https://issues.jboss.org/browse/SWSQE-526 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Filip Brychta > Priority: Major > > Currently when Kiali is released with older version than latest master, UI tests is not possible to run: > 1. UI tests are not tagged. > 2. Kiali REST Client is always latest on jenkins slaves. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3567) Import tab, with cards.

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3567?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3567: ------------------------------------- Thanks [~manstis], I know you guys will do your magic! :) The tab design is based off of a PatternFly pattern, not sure if the code example can offer a head-start? https://www.patternfly.org/pattern-library/content-views/card-view/#code > Import tab, with cards. > ----------------------- > > Key: DROOLS-3567 > URL: https://issues.jboss.org/browse/DROOLS-3567 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UXTeam, drools-tools > Attachments: Import-tab.pdf > > > Detail Import design as presented in: https://issues.jboss.org/browse/DROOLS-2999 > Specify any details not already covered by the patternfly card pattern: https://www.patternfly.org/pattern-library/content-views/card-view/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11670) Intermittent failures in EJBClientXidTransactionTestCase.testServerSuspension

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11670?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11670: ----------------------------------------- Thanks [~yersan]. Sounds like we need to be sure to get transaction-client released and upgrade before the final release. > Intermittent failures in EJBClientXidTransactionTestCase.testServerSuspension > ----------------------------------------------------------------------------- > > Key: WFLY-11670 > URL: https://issues.jboss.org/browse/WFLY-11670 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > Test started failing fairly frequently on Jan 11: > https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&bui... > https://ci.wildfly.org/project.html?projectId=WF&buildTypeId=&tab=testDet... > Perhaps that was related to https://github.com/wildfly/wildfly/pull/11913 which at a glance was the PR being tested in the first failure and may have been merged that day. So, [~yersan] I'm assigning to you to have a quick look. > I'll @Ignore the test. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11619) HA Singleton will not stop the service or deployment after merge the cluster-view if the elected node rejected by FullGC or suspended

by Wolf-Dieter Fink (Jira)

[ https://issues.jboss.org/browse/WFLY-11619?page=com.atlassian.jira.plugin... ] Wolf-Dieter Fink closed WFLY-11619. ----------------------------------- Resolution: Cannot Reproduce > HA Singleton will not stop the service or deployment after merge the cluster-view if the elected node rejected by FullGC or suspended > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11619 > URL: https://issues.jboss.org/browse/WFLY-11619 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 16.0.0.Beta1 > Reporter: Wolf-Dieter Fink > Assignee: Paul Ferraro > Priority: Critical > Attachments: node1.log, node2.log > > > If a 2 node cluster has a HA Singleton deployment (no matter whether it is a service or deployment) a merge after a split caused by FullGC will end in running two nodes as a Singleton provider. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3605) Invalid DMN file after migration 1.1 -> 1.2

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3605?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-3605: ---------------------------------------- I investigated this a bit further, and I _believe_ the recent introductions of ConstraintType is the culprit as making direct use of the `kie` prefix assuming is mapped to the internal namespace of "http://www.drools.org/kie/dmn/1.2"; although I'm still not 100% sure how does it get mapped while marshalled in the root Definitions node namespace map. > Invalid DMN file after migration 1.1 -> 1.2 > ------------------------------------------- > > Key: DROOLS-3605 > URL: https://issues.jboss.org/browse/DROOLS-3605 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniele Zonca > Assignee: Michael Anstis > Priority: Major > Attachments: dmn-daniele_after.dmn, dmn-daniele_before.dmn > > > `dmn-daniele_before.dmn` is a simple 1.1 DMN file. After migration (`dmn-daniele_after.dmn`) DMN model compilation fails with this error > [KBase: defaultKieBase]: DMN: Unable to resolve type reference 'kie.tSalary' on node 'Yearly Salary' (resource: com/dmn-daniele.dmn, DMN id: _8B521A18-C356-44D4-BEF0-123676DEDEE0, The listed type definition was not found) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11670) Intermittent failures in EJBClientXidTransactionTestCase.testServerSuspension

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-11670?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-11670: -------------------------------- Priority: Major (was: Critical) It seems the error is produced by WFTC-60, and show up in the wildfly test suite due to WFTC-54. So, looks like it is not a regression, so, I downgrade the level to major > Intermittent failures in EJBClientXidTransactionTestCase.testServerSuspension > ----------------------------------------------------------------------------- > > Key: WFLY-11670 > URL: https://issues.jboss.org/browse/WFLY-11670 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > Test started failing fairly frequently on Jan 11: > https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&bui... > https://ci.wildfly.org/project.html?projectId=WF&buildTypeId=&tab=testDet... > Perhaps that was related to https://github.com/wildfly/wildfly/pull/11913 which at a glance was the PR being tested in the first failure and may have been merged that day. So, [~yersan] I'm assigning to you to have a quick look. > I'll @Ignore the test. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-586) Switch kiali-qe-utils repository into GitLab

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-586?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-586: ------------------------------- Sprint: Kiali Sprint #18 (was: Kiali Sprint #18) > Switch kiali-qe-utils repository into GitLab > -------------------------------------------- > > Key: SWSQE-586 > URL: https://issues.jboss.org/browse/SWSQE-586 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Michael Foley > Priority: Optional > > Looks like internal GitLab[1] is ready to use. > We can move our kiali-qe-utils[2] to GitLab > Why? > * GitLab looks cool > * Friendly web code browser > * Review PR's > * integrate with CI (if needed) > * improves collaboration > We should get others feedback in our team on this task. > [1] - https://gitlab.cee.redhat.com > [2] - http://git.host.prod.eng.bos.redhat.com/git/kiali-qe-utils.git/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-587) Python broken in jenkins-slave-kiali-ui-tests-python3

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-587?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-587: -------------------------------- Sprint: Kiali Sprint #18 (was: Kiali Sprint #18) > Python broken in jenkins-slave-kiali-ui-tests-python3 > ----------------------------------------------------- > > Key: SWSQE-587 > URL: https://issues.jboss.org/browse/SWSQE-587 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > sh-4.2$ yum > sh: /usr/bin/yum: /usr/bin/python: bad interpreter: No such file or directory > sh-4.2$ python > sh: python: command not found > sh-4.2$ > Check other slaves as well -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 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 February 2019