[JBoss JIRA] (SWSQE-699) Code coverage for kiali
by Filip Brychta (Jira)
Filip Brychta created SWSQE-699:
-----------------------------------
Summary: Code coverage for kiali
Key: SWSQE-699
URL: https://issues.jboss.org/browse/SWSQE-699
Project: Kiali QE
Issue Type: Story
Reporter: Filip Brychta
Assignee: Filip Brychta
It would be nice to have code coverage report for kiali. We can generate report for all existing test suites.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup
by Ondrej Chaloupka (Jira)
[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ]
Ondrej Chaloupka reassigned WFLY-11858:
---------------------------------------
Fix Version/s: 17.0.0.Beta1
Assignee: Ondrej Chaloupka (was: Matěj Novotný)
Resolution: Done
> [Wildfly16] CDI fails to inject InitialContext during startup
> -------------------------------------------------------------
>
> Key: WFLY-11858
> URL: https://issues.jboss.org/browse/WFLY-11858
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Transactions
> Affects Versions: 16.0.0.Final
> Reporter: Rakesh Cherukuri
> Assignee: Ondrej Chaloupka
> Priority: Major
> Fix For: 17.0.0.Beta1
>
> Attachments: stacktrace.log
>
>
> We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error
> _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
> In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error.
> Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
> Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
> Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3702) [Stunner] Arrows are incorrectly positioned when save-open diagram
by Roger Martinez (Jira)
[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ]
Roger Martinez commented on DROOLS-3702:
----------------------------------------
Hey [~manstis] - I need some background on this, plz remember to also do a quick talk about this issue on our Submarine call tomorrow (Fri). Anyway I'll also keep in mind to talk about it! Thanks
> [Stunner] Arrows are incorrectly positioned when save-open diagram
> ------------------------------------------------------------------
>
> Key: DROOLS-3702
> URL: https://issues.jboss.org/browse/DROOLS-3702
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Daniel José dos Santos
> Assignee: Michael Anstis
> Priority: Major
> Labels: Stunner
> Attachments: auto-magnets.gif, fixed-magnets.gif, process-designer-connectors-magnets-issues.png, weird_arrow.gif
>
>
> 1. Add a `Decision Node`
> 2. Add a `Input Data Node` bellow `Decision Node`
> 3. Connect `Input Data Node` to `Decision Node`
> 4. Save
> 5. Close
> 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned.
> I noticed this in DMN Showcase and in drools-wb.
> And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month