[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-4503:
-------------------------------------
[~gabriolo] hello, I have question to clarify my understanding.
Is this jira about allowing user to put numbers always just without any suffix? (Long - l,L, Double - d,D, Float -f,F) ? Or is it the opposite way toa llow put numbers into scenario in any form?
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.26.0.Final
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation
> Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> !ErrorPopup.png|thumbnail!
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
> The worst consequence is that when user click "Apply", that literal is put inside the cell,
> !InsertedValue.png|thumbnail!
> and when sent to server it raise error (because server is expecting a number, not a string)
> !FollowError.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (SWSQE-838) Investigate how we could use git-crypt
by Michael Foley (Jira)
[ https://issues.jboss.org/browse/SWSQE-838?page=com.atlassian.jira.plugin.... ]
Michael Foley edited comment on SWSQE-838 at 9/10/19 9:49 AM:
--------------------------------------------------------------
[~pyadav] and praneeth. please take a look at this issue. it is an infra task. it will take some research. and perhaps a presentation to other qe's.
if you accept this task ... please add it to your fy2020 performance & development document ...
was (Author: mfoley):
[~pyadav] please take a look at this issue. it is an infra task. it will take some research. and perhaps a presentation to other qe's.
if you accept this task ... please add it to your fy2020 performance & development document ...
> Investigate how we could use git-crypt
> --------------------------------------
>
> Key: SWSQE-838
> URL: https://issues.jboss.org/browse/SWSQE-838
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Prachi Yadav
> Priority: Minor
> Labels: infrastructure
>
> Do we want to use git-crypt to store credentials?
> Problem is how to safely share credentials among team members, how to use them in jenkins jobs and automation, etc.
> # check how other teams are doing it
> # suggest improvements for kiali team
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFWIP-193) Is updating Kubernetes objects created by Operator supported?
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-193?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-193:
-----------------------------------
The recommendation is to not touch internal objects.
The Operator "owns" the underlying Kubernetes resources based on the WildFlyServer spec and may modify/delete them without notice to update its cluster state.
> Is updating Kubernetes objects created by Operator supported?
> -------------------------------------------------------------
>
> Key: WFWIP-193
> URL: https://issues.jboss.org/browse/WFWIP-193
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Technically it is possible to update Kubernetes objects which were created by Operator, e.g. StatefulSet, Pods, ...
> - Operator has its limitation compared to non-Operator approach (ports, volume mounts, deployment strategy, ...) So user may be tempted to tweak internal objects manually
> - But some values of internal objects are automatically synced with Operator (env,..). So even changed they are overwritten by original operator values after a while.
> What will be our general recommendation to users:
> - Dont touch internal objects?
> - We will document what can't be touched?
> - We will document what can be touched?
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFLY-12446) Memory leak in StatelessSessionComponent
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12446?page=com.atlassian.jira.plugin... ]
Cheng Fang edited comment on WFLY-12446 at 9/10/19 9:48 AM:
------------------------------------------------------------
Thanks [~jaikiran] for the detailed analysis. [~manovotn] can you take a look from Weld side, in particular why ejb bean instance holds {{CreationalContextImpl}}, which holds huge list containing thousands of {{org.jboss.weld.contexts.SerializableContextualInstanceImpl}}? I've updated the previously attached dump screenshot to show more weld classes.
was (Author: cfang):
Thanks @jaikiran for the detailed analysis. @manovotn can you take a look from Weld side, in particular why ejb bean instance holds {{CreationalContextImpl}}, which holds huge list containing thousands of {{org.jboss.weld.contexts.SerializableContextualInstanceImpl}}? I've updated the previously attached dump screenshot to show more weld classes.
> Memory leak in StatelessSessionComponent
> ----------------------------------------
>
> Key: WFLY-12446
> URL: https://issues.jboss.org/browse/WFLY-12446
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, EJB
> Affects Versions: 17.0.1.Final
> Reporter: Joerg Baesner
> Assignee: Cheng Fang
> Priority: Major
> Attachments: dump-weld.png, playground-jee8.zip, server.log.gz, wfly-12446-heap-dump.png
>
>
> When running the attached reproducer application and doing a memory analysis afterwards, it looks like a memory leak, e. g.
> {code}
> One instance of "org.jboss.as.ejb3.component.stateless.StatelessSessionComponent" loaded by "org.jboss.modules.ModuleClassLoader @ 0x5e0fbc2e0" occupies 936,593,520 (96.13%) bytes. The memory is accumulated in one instance of "java.util.concurrent.ConcurrentLinkedQueue$Node" loaded by "<system class loader>".
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4518) Implement UX styles for Test Coverage Report
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4518?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-4518:
-------------------------------------------
fyi [~srambach] - the team might need some of your time to get the styles implemented on their environment.
> Implement UX styles for Test Coverage Report
> --------------------------------------------
>
> Key: DROOLS-4518
> URL: https://issues.jboss.org/browse/DROOLS-4518
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: UX, UXTeam
> Attachments: Screen Shot 2019-09-10 at 9.35.23 AM.png, Screen Shot 2019-09-10 at 9.37.02 AM.png
>
>
> The implemented styles for the Test Coverage Report panel do not align with the HTML/CSS provided in jira https://issues.jboss.org/browse/DROOLS-3741.
> The styles used in the current implementation might present usability concerns - the Decision/Scenario list type size is very small and could pose a readability issue. The layout and alignment of the test summary data is difficult to scan, due to the gutter alignment.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4518) Implement UX styles for Test Coverage Report
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4518?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4518:
--------------------------------------
Labels: UX UXTeam (was: UX)
> Implement UX styles for Test Coverage Report
> --------------------------------------------
>
> Key: DROOLS-4518
> URL: https://issues.jboss.org/browse/DROOLS-4518
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: UX, UXTeam
> Attachments: Screen Shot 2019-09-10 at 9.35.23 AM.png, Screen Shot 2019-09-10 at 9.37.02 AM.png
>
>
> The implemented styles for the Test Coverage Report panel do not align with the HTML/CSS provided in jira https://issues.jboss.org/browse/DROOLS-3741.
> The styles used in the current implementation might present usability concerns - the Decision/Scenario list type size is very small and could pose a readability issue. The layout and alignment of the test summary data is difficult to scan, due to the gutter alignment.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4518) Implement UX styles for Test Coverage Report
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4518?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4518:
--------------------------------------
Attachment: Screen Shot 2019-09-10 at 9.37.02 AM.png
> Implement UX styles for Test Coverage Report
> --------------------------------------------
>
> Key: DROOLS-4518
> URL: https://issues.jboss.org/browse/DROOLS-4518
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: UX
> Attachments: Screen Shot 2019-09-10 at 9.35.23 AM.png, Screen Shot 2019-09-10 at 9.37.02 AM.png
>
>
> The implemented styles for the Test Coverage Report panel do not align with the HTML/CSS provided in jira https://issues.jboss.org/browse/DROOLS-3741.
> The styles used in the current implementation might present usability concerns - the Decision/Scenario list type size is very small and could pose a readability issue. The layout and alignment of the test summary data is difficult to scan, due to the gutter alignment.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4518) Implement UX styles for Test Coverage Report
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4518?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4518:
--------------------------------------
Attachment: Screen Shot 2019-09-10 at 9.35.23 AM.png
> Implement UX styles for Test Coverage Report
> --------------------------------------------
>
> Key: DROOLS-4518
> URL: https://issues.jboss.org/browse/DROOLS-4518
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: UX
> Attachments: Screen Shot 2019-09-10 at 9.35.23 AM.png, Screen Shot 2019-09-10 at 9.37.02 AM.png
>
>
> The implemented styles for the Test Coverage Report panel do not align with the HTML/CSS provided in jira https://issues.jboss.org/browse/DROOLS-3741.
> The styles used in the current implementation might present usability concerns - the Decision/Scenario list type size is very small and could pose a readability issue. The layout and alignment of the test summary data is difficult to scan, due to the gutter alignment.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months