[JBoss JIRA] (WFLY-13524) Update contributors.txt
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13524?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet edited comment on WFLY-13524 at 5/27/20 2:46 AM:
-------------------------------------------------------------------
I used {quote}git log --pretty=format:'%an <%ae>' | sort | uniq{quote}
So doing
{{git log --pretty=format:'%an <%ae>' | sort | uniq >> servlet-feature-pack/src/main/resources/content/copyright.txt}}
{{vi servlet-feature-pack/src/main/resources/content/copyright.txt}}
and using the {{:sort u}} command
was (Author: ehugonnet):
I used {quote}git log --pretty=format:'%an <%ae>' | sort | uniq{quote}
So doing
git log --pretty=format:'%an <%ae>' | sort | uniq >> servlet-feature-pack/src/main/resources/content/copyright.txt
vi servlet-feature-pack/src/main/resources/content/copyright.txt
and using the{quote} :sort u{quote} command
> Update contributors.txt
> -----------------------
>
> Key: WFLY-13524
> URL: https://issues.redhat.com/browse/WFLY-13524
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Emmanuel Hugonnet
> Priority: Minor
> Attachments: WFLY-13254-data.txt
>
>
> I'll attach the results of
> git shortlog --summary --email | sort | uniq
> That info can be integrated in with what's already there.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13524) Update contributors.txt
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13524?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet edited comment on WFLY-13524 at 5/27/20 2:45 AM:
-------------------------------------------------------------------
I used {quote}git log --pretty=format:'%an <%ae>' | sort | uniq{quote}
So doing
git log --pretty=format:'%an <%ae>' | sort | uniq >> servlet-feature-pack/src/main/resources/content/copyright.txt
vi servlet-feature-pack/src/main/resources/content/copyright.txt
and using the{quote} :sort u{quote} command
was (Author: ehugonnet):
I used {quote}git log --pretty=format:'%an <%ae>' | sort | uniq{quote}
> Update contributors.txt
> -----------------------
>
> Key: WFLY-13524
> URL: https://issues.redhat.com/browse/WFLY-13524
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Emmanuel Hugonnet
> Priority: Minor
> Attachments: WFLY-13254-data.txt
>
>
> I'll attach the results of
> git shortlog --summary --email | sort | uniq
> That info can be integrated in with what's already there.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13524) Update contributors.txt
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13524?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet edited comment on WFLY-13524 at 5/27/20 2:39 AM:
-------------------------------------------------------------------
I used {quote}git log --pretty=format:'%an <%ae>' | sort | uniq{quote}
was (Author: ehugonnet):
I used {quote}git log --pretty=format:%ae | sort | uniq{quote}
> Update contributors.txt
> -----------------------
>
> Key: WFLY-13524
> URL: https://issues.redhat.com/browse/WFLY-13524
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Emmanuel Hugonnet
> Priority: Minor
> Attachments: WFLY-13254-data.txt
>
>
> I'll attach the results of
> git shortlog --summary --email | sort | uniq
> That info can be integrated in with what's already there.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13524) Update contributors.txt
by Richard Opalka (Jira)
[ https://issues.redhat.com/browse/WFLY-13524?page=com.atlassian.jira.plugi... ]
Richard Opalka commented on WFLY-13524:
---------------------------------------
Note there might be some duplicities, e.g.:
---
Richard Opálka <opalka.richard(a)gmail.com>
Richard Opalka <ropalka(a)redhat.com>
Richard Opalka <opalka.richard(a)gmail.com>
---
But we probably don't care, do we?
> Update contributors.txt
> -----------------------
>
> Key: WFLY-13524
> URL: https://issues.redhat.com/browse/WFLY-13524
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Emmanuel Hugonnet
> Priority: Minor
> Attachments: WFLY-13254-data.txt
>
>
> I'll attach the results of
> git shortlog --summary --email | sort | uniq
> That info can be integrated in with what's already there.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13444) Observing High CPU in EPollArrayWrapper.epollCtl default I/O thread
by Srinivas ev (Jira)
[ https://issues.redhat.com/browse/WFLY-13444?page=com.atlassian.jira.plugi... ]
Srinivas ev commented on WFLY-13444:
------------------------------------
Hi [~flavia.rainone], any update on this JIRA. Can you please have a look, as this is blocking one of our delivery.
> Observing High CPU in EPollArrayWrapper.epollCtl default I/O thread
> -------------------------------------------------------------------
>
> Key: WFLY-13444
> URL: https://issues.redhat.com/browse/WFLY-13444
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Srinivas ev
> Assignee: Flavia Rainone
> Priority: Critical
> Attachments: IO thread memory.PNG, IO thread.PNG, Thread consuming high CPU.PNG, ThreadDump1set.zip, ThreadDump2set.zip, default IO thread 73.PNG, default io consuming snapshot.PNG, default io consuming.PNG, stack trace from snapshot.PNG, stack trace in thread dump.PNG, threaddump-1589514505334.tdump, top command output.PNG
>
>
> Facing high CPU by one of the default I/O thread In Wildfly 10.1.0 Final. Looks none of our application component thread is consuming.
> Can somebody check what is triggering this issue? I attached the thread stack to this Jira. This is blocking our releases. When the CPU cores are high in number, multiple default I/O threads will kick in consuming the CPU in 90~100% range continuously.
> Wildfly 10.1.0 Final
> Java -
> openjdk version "1.8.0_232"
> OpenJDK Runtime Environment (build 1.8.0_232-b09)
> OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode
> ---------------------------------------------------------------------------------------------------
> at java.lang.Throwable.fillInStackTrace(Native Method)
> at java.lang.Throwable.fillInStackTrace(Throwable.java:784)
> at java.lang.Throwable.<init>(Throwable.java:251)
> at java.lang.Exception.<init>(Exception.java:54)
> at java.io.IOException.<init>(IOException.java:47)
> at java.nio.channels.ClosedChannelException.<init>(ClosedChannelException.java:52)
> at org.xnio.ssl.JsseStreamConduit.write(JsseStreamConduit.java:1022)
> at org.xnio.conduits.ConduitStreamSinkChannel.write(ConduitStreamSinkChannel.java:150)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:385)
> at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:372)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.WriteReadyHandler$ChannelListenerHandler.writeReady(WriteReadyHandler.java:65)
> at org.xnio.ssl.JsseStreamConduit.run(JsseStreamConduit.java:393)
> at org.xnio.ssl.JsseStreamConduit.readReady(JsseStreamConduit.java:547)
> at org.xnio.ssl.JsseStreamConduit$2.readReady(JsseStreamConduit.java:319)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
> -------------------------------------------------------------------------------------------
> at sun.nio.ch.EPollArrayWrapper.epollCtl(Native Method)
> at sun.nio.ch.EPollArrayWrapper.updateRegistrations(EPollArrayWrapper.java:299)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:268)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:515)
> -----------------------------------------------------------------------------------
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5380) Odd Behavior in Calendars for java.util.Date fields in Guided Rule Editor
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5380?page=com.atlassian.jira.plug... ]
Toni Rikkola updated DROOLS-5380:
---------------------------------
Priority: Critical (was: Blocker)
> Odd Behavior in Calendars for java.util.Date fields in Guided Rule Editor
> -------------------------------------------------------------------------
>
> Key: DROOLS-5380
> URL: https://issues.redhat.com/browse/DROOLS-5380
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.33.0.Final
> Reporter: Trisula Siripurapu
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: drools-tools
> Attachments: After I click on May 30 it Shows May 29th in Column.jpg, Before Selecting May 30 date.jpg, But the Source Tab shows May 30th.jpg
>
>
> I am using Decision Central 7.33.0.Final
> Chrome - Version 81.0.4044.113 (Official Build) (64-bit)
> I have a Date field which is templatized in a rule condition in a guided rule template. In the 'Data' tab when I go pick a date for this template key, the column is not showing the date I pick. It shows a date which is one day earlier. For example, if I pick in the calendar May 30th, 2020 the actual column in the 'Data' tab shows 29-May-2020. The 'Source' tab shows the right date though. For a business user it is confusing as they do not see the date they pick in the column.
> I have attached some screen shots here.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years