[JBoss JIRA] (DROOLS-2827) [DMN Designer] Diagram save produces svg
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2827?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2827:
----------------------------------------
[~jomarko] The BPMN Editor does not save multiple versions (it uses the same file name each time it is saved) so something in DMN is amiss.
[~tirelli] Stunner provides the ability to export JPG, PNG, PDF, SVG and XML from the toolbar. This JIRA represents the behaviour of a DMN SVG file being automatically created and saved whenever the DMN file is saved.. i.e. no User interaction required to generate the SVG file other than saving the DMN file in the editor.
> [DMN Designer] Diagram save produces svg
> ----------------------------------------
>
> Key: DROOLS-2827
> URL: https://issues.jboss.org/browse/DROOLS-2827
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: Screenshot from 2018-08-02 10-56-15.png
>
>
> When user saves the diagram, the svg file appears in the workbench.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10796) Warning about JSF version 'NONE' is shown in logs
by Jan Kašík (JIRA)
Jan Kašík created WFLY-10796:
--------------------------------
Summary: Warning about JSF version 'NONE' is shown in logs
Key: WFLY-10796
URL: https://issues.jboss.org/browse/WFLY-10796
Project: WildFly
Issue Type: Bug
Components: JSF
Affects Versions: 14.0.0.CR1
Reporter: Jan Kašík
Assignee: Farah Juma
Following warning is shown in log upon server start:
{code}
2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
{code}
Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (SWSQE-372) Github - API rate limit exceeded for 66.187.233.206.
by Filip Brychta (JIRA)
Filip Brychta created SWSQE-372:
-----------------------------------
Summary: Github - API rate limit exceeded for 66.187.233.206.
Key: SWSQE-372
URL: https://issues.jboss.org/browse/SWSQE-372
Project: Kiali QE
Issue Type: QE Task
Reporter: Filip Brychta
Assignee: Michael Foley
We have only 60 requests/hour and I already hit problem with:
sh-4.2$ curl -L -s https://api.github.com/repos/istio/istio/releases/latest
{
"message": "API rate limit exceeded for 66.187.233.206. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
"documentation_url": "https://developer.github.com/v3/#rate-limiting"
}
Here is more info:
sh-4.2$ curl -i https://api.github.com/users/octocat
HTTP/1.1 403 Forbidden
Server: GitHub.com
Date: Mon, 06 Aug 2018 10:49:13 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 258
Status: 403 Forbidden
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1533552848
X-GitHub-Media-Type: github.v3; format=json
Access-Control-Expose-Headers: ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
Access-Control-Allow-Origin: *
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: deny
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin
Content-Security-Policy: default-src 'none'
X-Runtime-rack: 0.014340
X-GitHub-Request-Id: CFC8:1D6B:174D41B:2D510DA:5B6827A9
{
"message": "API rate limit exceeded for 66.187.233.206. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
"documentation_url": "https://developer.github.com/v3/#rate-limiting"
}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2829) [DMN Designer] Expression header cell is not updated from properties panel
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2829?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2829:
----------------------------------------
[~jomarko] I also re-tested with the {{kie-wb}} WAR you linked, from an anonymous Chrome tab (to ensure it wasn't using anything cached) and it was OK too.
> [DMN Designer] Expression header cell is not updated from properties panel
> --------------------------------------------------------------------------
>
> Key: DROOLS-2829
> URL: https://issues.jboss.org/browse/DROOLS-2829
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Labels: drools-tools
>
> Decision and BKM elements holds some expression inside. This expression can be edited via expression grid editor. The expression grid editor shows the name of the parent element in its header cell. The problem is that this header cell is not updated if the element name is updated form the properties panel while expression grid editor is opened.
> Spotted during DROOLS-2755 review. Not sure if it is related.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2829) [DMN Designer] Expression header cell is not updated from properties panel
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2829?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2829:
-----------------------------------
Story Points: 1
Sprint: 2018 Week 30-32
> [DMN Designer] Expression header cell is not updated from properties panel
> --------------------------------------------------------------------------
>
> Key: DROOLS-2829
> URL: https://issues.jboss.org/browse/DROOLS-2829
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Labels: drools-tools
>
> Decision and BKM elements holds some expression inside. This expression can be edited via expression grid editor. The expression grid editor shows the name of the parent element in its header cell. The problem is that this header cell is not updated if the element name is updated form the properties panel while expression grid editor is opened.
> Spotted during DROOLS-2755 review. Not sure if it is related.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-89) [Artemis 2.x Upgrade] Clients do not failover to backup when force-failover operation is used with JDBC store
by Martin Styk (JIRA)
[ https://issues.jboss.org/browse/WFWIP-89?page=com.atlassian.jira.plugin.s... ]
Martin Styk updated WFWIP-89:
-----------------------------
Description:
Dedicated topology (1live, 1 backup) with JDBC store (oracle12c).
Force failover operation is called on live node. Live artemis server stops, however backup doesn't start.
This issue is intermittent.
Attaching logs.
was:
Dedicated topology (1live, 1 backup) with JDBC store (oracle12c).
Force failover operation is called on live node. Live artemis server stops, however backup doesn't start.
Attaching logs.
> [Artemis 2.x Upgrade] Clients do not failover to backup when force-failover operation is used with JDBC store
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-89
> URL: https://issues.jboss.org/browse/WFWIP-89
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Martin Styk
> Assignee: Martyn Taylor
> Attachments: org.jboss.qa.artemis.test.failover.DedicatedFailoverTestCase20.testForceFailoverOperation.zip
>
>
> Dedicated topology (1live, 1 backup) with JDBC store (oracle12c).
> Force failover operation is called on live node. Live artemis server stops, however backup doesn't start.
> This issue is intermittent.
> Attaching logs.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months