[Red Hat JIRA] (WFLY-11638) MP Metrics - sort alphabetically /metrics output
by Rostislav Svoboda (Jira)
[ https://issues.redhat.com/browse/WFLY-11638?page=com.atlassian.jira.plugi... ]
Rostislav Svoboda commented on WFLY-11638:
------------------------------------------
Hi [~jaslee]. I'm no longer on EAP QE team, CCing [~msvehla] (EAP QE lead) to be notified about this JIRA.
WFLY is community tracker, so I think it's fine to move to Closed state + set the fix version if you will be able to identify it.
> MP Metrics - sort alphabetically /metrics output
> ------------------------------------------------
>
> Key: WFLY-11638
> URL: https://issues.redhat.com/browse/WFLY-11638
> Project: WildFly
> Issue Type: Enhancement
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jason Lee
> Priority: Major
>
> MP Metrics - sort alphabetically /metrics output
> When playing with https://github.com/wildfly/wildfly/pull/11949 I got upset about metrics not being sorted alphabetically or at least grouped together.
> My use case was to look at wildfly_undertow_** metrics via browser.
> base: and vendor: metrics are grouped together, WF subsystem metrics not - e.g. wildfly_undertow_** metrics were listed on 4 different places.
> If alphabetical order is not easy to be achieved, subsystem metrics should be at least grouped together.
> I know machines do not care about the order, but people have to look at /metrics too (from time to time ...).
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-6042) Actual text value instead of tip
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6042?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-6042:
-------------------------------------
Description:
When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
That leads to
1) when editing, the user have to cancel that string before (not expected, giving the shown message)
2) if not edited, the name of the field remains the proposed one.
If that proposed string should serve a s default/auto generated value, it would be better no not use a "do that" sentence.
Attached screens.
If a "do that" string is to be used, then it should be shown as in the "Search data type" search combo
was:
When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
That leads to
1) when editing, the user have to cancel that string before
2) if not edited, the name of the field remains the proposed one.
If that proposed string should serve a s default/auto generated value, it would be better no not use a "do that" sentence.
Attached screens.
If a "do that" string is to be used, then it should be shown as in the "Search data type" search combo
> Actual text value instead of tip
> --------------------------------
>
> Key: DROOLS-6042
> URL: https://issues.redhat.com/browse/DROOLS-6042
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.50.0.Final
> Reporter: Gabriele Cardosi
> Assignee: Mario Fusco
> Priority: Major
> Attachments: CreatedField.png, CreationField.png, ExpectedBehavior.png
>
>
> When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
> That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
> That leads to
> 1) when editing, the user have to cancel that string before (not expected, giving the shown message)
> 2) if not edited, the name of the field remains the proposed one.
> If that proposed string should serve a s default/auto generated value, it would be better no not use a "do that" sentence.
> Attached screens.
> If a "do that" string is to be used, then it should be shown as in the "Search data type" search combo
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-6042) Actual text value instead of tip
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6042?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-6042:
-------------------------------------
Description:
When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
That leads to
1) when editing, the user have to cancel that string before
2) if not edited, the name of the field remains the proposed one.
If that proposed string should serve a s default/auto generated value, it would be better no not use a "do that" sentence.
Attached screens.
If a "do that" string is to be used, then it should be shown as in the "Search data type" search combo
was:
When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
That leads to
1) when editing, the user have to cancel that string before
2) if not edited, the name of the field remains the proposed one.
If that proposed string should serve a s default/autogenerated value, it would be better no not use a "do that" sentence.
Attached screens
> Actual text value instead of tip
> --------------------------------
>
> Key: DROOLS-6042
> URL: https://issues.redhat.com/browse/DROOLS-6042
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.50.0.Final
> Reporter: Gabriele Cardosi
> Assignee: Mario Fusco
> Priority: Major
> Attachments: CreatedField.png, CreationField.png, ExpectedBehavior.png
>
>
> When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
> That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
> That leads to
> 1) when editing, the user have to cancel that string before
> 2) if not edited, the name of the field remains the proposed one.
> If that proposed string should serve a s default/auto generated value, it would be better no not use a "do that" sentence.
> Attached screens.
> If a "do that" string is to be used, then it should be shown as in the "Search data type" search combo
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-6042) Actual text value instead of tip
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6042?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-6042:
-------------------------------------
Attachment: ExpectedBehavior.png
> Actual text value instead of tip
> --------------------------------
>
> Key: DROOLS-6042
> URL: https://issues.redhat.com/browse/DROOLS-6042
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.50.0.Final
> Reporter: Gabriele Cardosi
> Assignee: Mario Fusco
> Priority: Major
> Attachments: CreatedField.png, CreationField.png, ExpectedBehavior.png
>
>
> When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
> That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
> That leads to
> 1) when editing, the user have to cancel that string before
> 2) if not edited, the name of the field remains the proposed one.
> If that proposed string should serve a s default/autogenerated value, it would be better no not use a "do that" sentence.
> Attached screens
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-6042) Actual text value instead of tip
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6042?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-6042:
-------------------------------------
Attachment: CreatedField.png
> Actual text value instead of tip
> --------------------------------
>
> Key: DROOLS-6042
> URL: https://issues.redhat.com/browse/DROOLS-6042
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.50.0.Final
> Reporter: Gabriele Cardosi
> Assignee: Mario Fusco
> Priority: Major
> Attachments: CreatedField.png, CreationField.png, ExpectedBehavior.png
>
>
> When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
> That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
> That leads to
> 1) when editing, the user have to cancel that string before
> 2) if not edited, the name of the field remains the proposed one.
> If that proposed string should serve a s default/autogenerated value, it would be better no not use a "do that" sentence.
> Attached screens
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-6042) Actual text value instead of tip
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6042?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-6042:
-------------------------------------
Attachment: CreationField.png
> Actual text value instead of tip
> --------------------------------
>
> Key: DROOLS-6042
> URL: https://issues.redhat.com/browse/DROOLS-6042
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.50.0.Final
> Reporter: Gabriele Cardosi
> Assignee: Mario Fusco
> Priority: Major
> Attachments: CreationField.png
>
>
> When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
> That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
> That leads to
> 1) when editing, the user have to cancel that string before
> 2) if not edited, the name of the field remains the proposed one.
> If that proposed string should serve a s default/autogenerated value, it would be better no not use a "do that" sentence.
> Attached screens
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-6042) Actual text value instead of tip
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-6042:
----------------------------------------
Summary: Actual text value instead of tip
Key: DROOLS-6042
URL: https://issues.redhat.com/browse/DROOLS-6042
Project: Drools
Issue Type: Bug
Affects Versions: 7.50.0.Final
Reporter: Gabriele Cardosi
Assignee: Mario Fusco
When creating a new DataType, inside the "Name" text box a String "Insert a name" is shown.
That string is a tip, and as such should be shown, but in reality it is the actual value of that text box.
That leads to
1) when editing, the user have to cancel that string before
2) if not edited, the name of the field remains the proposed one.
If that proposed string should serve a s default/autogenerated value, it would be better no not use a "do that" sentence.
Attached screens
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (WFLY-14044) Indexing org.postgresq.jdbc.PgConnection$1 fails
by Tobias Stadler (Jira)
[ https://issues.redhat.com/browse/WFLY-14044?page=com.atlassian.jira.plugi... ]
Tobias Stadler commented on WFLY-14044:
---------------------------------------
Seems to be fixed with https://github.com/pgjdbc/pgjdbc/pull/2010
> Indexing org.postgresq.jdbc.PgConnection$1 fails
> ------------------------------------------------
>
> Key: WFLY-14044
> URL: https://issues.redhat.com/browse/WFLY-14044
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 18.0.0.Final
> Reporter: Tobias Stadler
> Assignee: Jason Greene
> Priority: Major
>
> If I package postgresql-42.2.18.jar in a war, jandex fails to index it:
> {code:java}
> 09:15:26,059 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0003: Could not index class org/postgresql/jdbc/PgConnection$1.class at /content/foo.war/WEB-INF/lib/postgresql-42.2.18.jar: java.lang.IllegalStateException: Required class information is missing09:15:26,059 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0003: Could not index class org/postgresql/jdbc/PgConnection$1.class at /content/foo.war/WEB-INF/lib/postgresql-42.2.18.jar: java.lang.IllegalStateException: Required class information is missing at org.jboss.jandex.Indexer.rebuildNestedType(Indexer.java:926) at org.jboss.jandex.Indexer.resolveTypePath(Indexer.java:786) at org.jboss.jandex.Indexer.resolveTypeAnnotation(Indexer.java:705) at org.jboss.jandex.Indexer.resolveTypeAnnotations(Indexer.java:613) at org.jboss.jandex.Indexer.index(Indexer.java:1602) at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:99) at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363) at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-5976) [DMN Editor] Reordering non-Structure types may cause conversion to Structure
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5976?page=com.atlassian.jira.plug... ]
Gabriele Cardosi commented on DROOLS-5976:
------------------------------------------
The behavior somehow is still present, but hos I see it is
-> if you drag the field over another one (the other one becoming highlighted) it will nest under it, turning the latter into a Structure
-> if you drag the field below or above another one (the other one not becoming highlighted) it will not nest under
I do not know if it is wanted behavior, related to comment
"Expected: if you drag a field over a non-Structure field, I would expect such non-Structure field NOT to be converted into a Structure, and thus NOT nest the field you are dragging under it"
> [DMN Editor] Reordering non-Structure types may cause conversion to Structure
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5976
> URL: https://issues.redhat.com/browse/DROOLS-5976
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.49.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Guilherme Gomes
> Priority: Major
> Attachments: reorder-2.webm, reorder.webm
>
>
> Reordering fields is a bit error prone, one shaky hand may result in changing the type of a field to Structure.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month
[Red Hat JIRA] (DROOLS-6041) "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-6041?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-6041:
--------------------------------------
Priority: Major (was: Minor)
> "RHS doesn't have a type" error when a semicolon is missing with exec-model and mvel dialect
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-6041
> URL: https://issues.redhat.com/browse/DROOLS-6041
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.50.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> With a rule like this: (See, a semicolon is missing in the "p2.age = 30" line)
> {noformat}
> rule R
> dialect "mvel"
> when
> Person(name == "Mario")
> then
> Person p2 = new Person("John");
> p2.age = 30
> insert(p2);
> end
> {noformat}
> exec-model fails with
> {noformat}
> CompilationProblemErrorResult: org.drools.mvelcompiler.MvelCompilerException: RHS doesn't have a type
> {noformat}
> while standard-drl runs successfully.
> I'm not sure if exec-model should work the same as standard-drl (treat a new line as a delimiter?), or give a better error message.
> This looks to be a rare issue but when using spreadsheet, it's possible to forget to add a semicolon. (Then users don't notice the mistake because standard-drl executes it succesfully)
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 1 month