[JBoss JIRA] (SWSQE-695) Map Jira Workflows To Tablue Graphs
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-695?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-695:
----------------------------------
Sprint: Kiali Sprint #23, Kiali Sprint #24 (was: Kiali Sprint #23)
> Map Jira Workflows To Tablue Graphs
> -----------------------------------
>
> Key: SWSQE-695
> URL: https://issues.jboss.org/browse/SWSQE-695
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matthew Mahoney
> Assignee: Prachi Yadav
> Priority: Major
> Labels: pqi
>
> Two parts to this task:
> 1) Because only a couple team members have access to Tablue, generate Kiali metric graphs in Tablue and Paste them into a team accessablel doc so that we can analyze these metrics
> 2) Map Jira Workflow queries to Tablue graphs, so that we can better understand how each of the Tablue graphs are generated.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12206) Dependencies - micro version bump
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFLY-12206:
----------------------------------------
Summary: Dependencies - micro version bump
Key: WFLY-12206
URL: https://issues.jboss.org/browse/WFLY-12206
Project: WildFly
Issue Type: Task
Reporter: Rostislav Svoboda
Assignee: Brian Stansberry
Dependencies - micro version bump
Several components have newer versions available
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4194) [DMN Designer] Date And Time constraint placeholders
by Jozef Marko (Jira)
Jozef Marko created DROOLS-4194:
-----------------------------------
Summary: [DMN Designer] Date And Time constraint placeholders
Key: DROOLS-4194
URL: https://issues.jboss.org/browse/DROOLS-4194
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.24.0.Final
Reporter: Jozef Marko
Assignee: Daniel José dos Santos
Attachments: date-time-chrome.png, date-time-firefox.png
The placeholders *Insert a value* for Date and Time constraint are not well readable as on firefox so on chrome, see the attached screenshots.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3755) [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Date/Time" component when the type is "Date/Time"
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3755?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3755:
--------------------------------
Description:
When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows:
Enum/Range:
!datetime-enum.png|thumbnail!
!datetime-range.png|thumbnail!
Components:
!datetime-dropdown.png|thumbnail!
!datetime-time.png|thumbnail!
⚠️ Notice:
This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665):
- An input with the timepicker;
- A toggle button (to toggle between offset and timezone)
- An input which is filled accordingly to the toggle button
h2. Acceptance test
Both on Firefox (x) and Chrome (/)
- Enumeration, Save and reopen (/)
- Range, Save and reopen (x) [^date-time-range.webm]
- Expression, Save and reopen (/)
- Change constraint, both date and time (/)
- Change constraint, just time (/)
- Change constraint, just date (/)
- Build and deploy project where date/time constraint in use
h3. Re-review
Issues form acceptance test fixed (/)
was:
When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows:
Enum/Range:
!datetime-enum.png|thumbnail!
!datetime-range.png|thumbnail!
Components:
!datetime-dropdown.png|thumbnail!
!datetime-time.png|thumbnail!
⚠️ Notice:
This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665):
- An input with the timepicker;
- A toggle button (to toggle between offset and timezone)
- An input which is filled accordingly to the toggle button
h2. Acceptance test
Both on Firefox (x) and Chrome (/)
- Enumeration, Save and reopen (/)
- Range, Save and reopen (x) [^date-time-range.webm]
- Expression, Save and reopen (/)
- Change constraint, both date and time (/)
- Change constraint, just time (/)
- Change constraint, just date (/)
- Build and deploy project where date/time constraint in use
> [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Date/Time" component when the type is "Date/Time"
> --------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3755
> URL: https://issues.jboss.org/browse/DROOLS-3755
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: date-time-range.webm, datetime-dropdown.png, datetime-enum.png, datetime-range.png, datetime-time.png, dt-firefox-1.png, dt-firefox-2.png
>
>
> When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows:
> Enum/Range:
> !datetime-enum.png|thumbnail!
> !datetime-range.png|thumbnail!
> Components:
> !datetime-dropdown.png|thumbnail!
> !datetime-time.png|thumbnail!
> ⚠️ Notice:
> This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665):
> - An input with the timepicker;
> - A toggle button (to toggle between offset and timezone)
> - An input which is filled accordingly to the toggle button
> h2. Acceptance test
> Both on Firefox (x) and Chrome (/)
> - Enumeration, Save and reopen (/)
> - Range, Save and reopen (x) [^date-time-range.webm]
> - Expression, Save and reopen (/)
> - Change constraint, both date and time (/)
> - Change constraint, just time (/)
> - Change constraint, just date (/)
> - Build and deploy project where date/time constraint in use
> h3. Re-review
> Issues form acceptance test fixed (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3755) [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Date/Time" component when the type is "Date/Time"
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3755?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3755:
--------------------------------
Description:
When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows:
Enum/Range:
!datetime-enum.png|thumbnail!
!datetime-range.png|thumbnail!
Components:
!datetime-dropdown.png|thumbnail!
!datetime-time.png|thumbnail!
⚠️ Notice:
This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665):
- An input with the timepicker;
- A toggle button (to toggle between offset and timezone)
- An input which is filled accordingly to the toggle button
h2. Acceptance test
Both on Firefox (x) and Chrome (/)
- Enumeration, Save and reopen (/)
- Range, Save and reopen (x) [^date-time-range.webm]
- Expression, Save and reopen (/)
- Change constraint, both date and time (/)
- Change constraint, just time (/)
- Change constraint, just date (/)
- Build and deploy project where date/time constraint in use
h3. Re-review
Issues from acceptance test fixed (/)
was:
When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows:
Enum/Range:
!datetime-enum.png|thumbnail!
!datetime-range.png|thumbnail!
Components:
!datetime-dropdown.png|thumbnail!
!datetime-time.png|thumbnail!
⚠️ Notice:
This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665):
- An input with the timepicker;
- A toggle button (to toggle between offset and timezone)
- An input which is filled accordingly to the toggle button
h2. Acceptance test
Both on Firefox (x) and Chrome (/)
- Enumeration, Save and reopen (/)
- Range, Save and reopen (x) [^date-time-range.webm]
- Expression, Save and reopen (/)
- Change constraint, both date and time (/)
- Change constraint, just time (/)
- Change constraint, just date (/)
- Build and deploy project where date/time constraint in use
h3. Re-review
Issues form acceptance test fixed (/)
> [DMN Designer] Data Types - Constraints (Range/Enumeration) - Add "Date/Time" component when the type is "Date/Time"
> --------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3755
> URL: https://issues.jboss.org/browse/DROOLS-3755
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: date-time-range.webm, datetime-dropdown.png, datetime-enum.png, datetime-range.png, datetime-time.png, dt-firefox-1.png, dt-firefox-2.png
>
>
> When the type of the Data Type is "Date/Time", add the "Date/Time" component to the input, as the following mockup shows:
> Enum/Range:
> !datetime-enum.png|thumbnail!
> !datetime-range.png|thumbnail!
> Components:
> !datetime-dropdown.png|thumbnail!
> !datetime-time.png|thumbnail!
> ⚠️ Notice:
> This component has some elements from the time component (https://issues.jboss.org/browse/DROOLS-3665):
> - An input with the timepicker;
> - A toggle button (to toggle between offset and timezone)
> - An input which is filled accordingly to the toggle button
> h2. Acceptance test
> Both on Firefox (x) and Chrome (/)
> - Enumeration, Save and reopen (/)
> - Range, Save and reopen (x) [^date-time-range.webm]
> - Expression, Save and reopen (/)
> - Change constraint, both date and time (/)
> - Change constraint, just time (/)
> - Change constraint, just date (/)
> - Build and deploy project where date/time constraint in use
> h3. Re-review
> Issues from acceptance test fixed (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4287) CLI should show not show default value once value one of "alternatives" attributes was set
by Michal Petrov (Jira)
[ https://issues.jboss.org/browse/WFCORE-4287?page=com.atlassian.jira.plugi... ]
Michal Petrov commented on WFCORE-4287:
---------------------------------------
[~brian.stansberry], unless I'm missing something we only need to modify ReadAttributeHandler to not supply the default value if the model has alternatives, however doing so breaks legacy tests. Is there a way to resolve that?
> CLI should show not show default value once value one of "alternatives" attributes was set
> ------------------------------------------------------------------------------------------
>
> Key: WFCORE-4287
> URL: https://issues.jboss.org/browse/WFCORE-4287
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Management
> Reporter: Miroslav Novak
> Priority: Major
>
> If there are attributes which are "alternatives" and both of them are undefined then default value of one of the attributes is shown in CLI, for example:
> {code}
> [standalone@localhost:9990 /] ls /subsystem=messaging-activemq/server=default
> elytron-domain=undefined
> security-domain=other
> {code}
> at this moment when I try set elytron-domain:
> {code}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:write-attribute(name=elytron-domain,value=ApplicationRealm)
> {code}
> then it shows:
> {code}
> [standalone@localhost:9990 /] ls /subsystem=messaging-activemq/server=default
> elytron-domain=ApplicationDomain
> security-domain=other
> {code}
> Can this be changed that it would show {{security-domain=undefined}} so it would not show default values anymore? Current display is confusing as it's not clear what is used.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11601) Weld vs Undertow bootstrap: Race condition
by Matěj Novotný (Jira)
[ https://issues.jboss.org/browse/WFLY-11601?page=com.atlassian.jira.plugin... ]
Matěj Novotný resolved WFLY-11601.
----------------------------------
Resolution: Duplicate
Awesome, thanks for verification!
I'll close this issue as a duplicate of the WELD one.
WFLY will have the fix with update to Weld 3.1.2.Final.
> Weld vs Undertow bootstrap: Race condition
> ------------------------------------------
>
> Key: WFLY-11601
> URL: https://issues.jboss.org/browse/WFLY-11601
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Web (Undertow)
> Affects Versions: 15.0.1.Final
> Reporter: Stefan Gr
> Assignee: Matěj Novotný
> Priority: Major
> Attachments: TestApp.zip, TestLib.zip, changes.diff, deploy-failed.txt, deploy-mixed-success.txt, deploy-success.txt, test-app-1.0.0.war, weld-core-impl-3.0.5.Final.jar, weld-core-impl-3.0.5.Final.jar
>
>
> WFLY-9732 / WFLY-10784 moves the completion of WELD from the WeldStartService to WeldStartCompetionService. This causes a race condition with the UndertowDeploymentService which executes the servlet listeners for context-initialized which again fires ApplicationScope-initialized events in CDI.
> You can find more in [WELD-2557|https://issues.jboss.org/browse/WELD-2557?focusedCommentId=1368...].
> In short: WeldStartCompletionService and UndertowDeploymentService pushes the logic to the executor service. It may happen, that the logik of undertow runs before the weld completion. Events fired in the servlet listeners won't find all event observers.
> A possible solution would bo to set the WeldStartCompletionService as a dependency of the UndertowDeploymentService
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled
by Michal Petrov (Jira)
[ https://issues.jboss.org/browse/WFLY-11933?page=com.atlassian.jira.plugin... ]
Michal Petrov commented on WFLY-11933:
--------------------------------------
[~dlofthouse], [~jmesnil], what I'm observing is this:
{code:title=CLI user}
SecurityIdentity{
principal=$local@ManagementRealm,
securityDomain=org.wildfly.security.auth.server.SecurityDomain@f08ba56,
authorizationIdentity=EMPTY,
realmInfo=RealmInfo{
name='LOCAL',
securityRealm=org.jboss.as.domain.management.security.SecurityRealmService$SharedStateSecurityRealm@e88dd09
},
creationTime=2019-06-13T12:37:22.741Z
}
{code}
{code:title=Web user}
SecurityIdentity{
principal=anonymous,
securityDomain=org.wildfly.security.auth.server.SecurityDomain@453bb70,
authorizationIdentity=EMPTY,
realmInfo=RealmInfo{
name='default',
securityRealm=EMPTY_REALM
},
creationTime=2019-06-13T12:33:24.307Z
}
{code}
The user accessing localhost has no authorization, should they be granted a SuperUser status?
> Error when accessing metrics with RBAC enabled
> ----------------------------------------------
>
> Key: WFLY-11933
> URL: https://issues.jboss.org/browse/WFLY-11933
> Project: WildFly
> Issue Type: Bug
> Components: Management, MP Metrics
> Affects Versions: 16.0.0.Final, 17.0.0.Final
> Reporter: Claudio Weiler
> Assignee: Jeff Mesnil
> Priority: Major
>
> When RBAC is enabled for management in Wildfly 16, metrics throws exception:
> java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [
> ("subsystem" => "datasources"),
> ("data-source" => "ExampleDS"),
> ("statistics" => "pool")
> ]: "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\"),
> (\"statistics\" => \"pool\")
> ]' not found".
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11601) Weld vs Undertow bootstrap: Race condition
by Stefan Gr (Jira)
[ https://issues.jboss.org/browse/WFLY-11601?page=com.atlassian.jira.plugin... ]
Stefan Gr commented on WFLY-11601:
----------------------------------
Sorry, I had some problems building WELD behind the company proxy (some dependencies couldn't be resolved)...
I've just installed your weld version to the WF15 testserver I have and restartet it multiple times using my test application.
I got no errors at all. Even the real world applications seem to work just fine.
> Weld vs Undertow bootstrap: Race condition
> ------------------------------------------
>
> Key: WFLY-11601
> URL: https://issues.jboss.org/browse/WFLY-11601
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Web (Undertow)
> Affects Versions: 15.0.1.Final
> Reporter: Stefan Gr
> Assignee: Matěj Novotný
> Priority: Major
> Attachments: TestApp.zip, TestLib.zip, changes.diff, deploy-failed.txt, deploy-mixed-success.txt, deploy-success.txt, test-app-1.0.0.war, weld-core-impl-3.0.5.Final.jar, weld-core-impl-3.0.5.Final.jar
>
>
> WFLY-9732 / WFLY-10784 moves the completion of WELD from the WeldStartService to WeldStartCompetionService. This causes a race condition with the UndertowDeploymentService which executes the servlet listeners for context-initialized which again fires ApplicationScope-initialized events in CDI.
> You can find more in [WELD-2557|https://issues.jboss.org/browse/WELD-2557?focusedCommentId=1368...].
> In short: WeldStartCompletionService and UndertowDeploymentService pushes the logic to the executor service. It may happen, that the logik of undertow runs before the weld completion. Events fired in the servlet listeners won't find all event observers.
> A possible solution would bo to set the WeldStartCompletionService as a dependency of the UndertowDeploymentService
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months