Re: Allocation Instrumenter

(Added Jeremy Manson and Ami Fischman to recipients) Guys, we're interested in fixing this concurrency bug in AllocationRecorder: https://github.com/google/allocation-instrumenter/issues/15 What would be the best way to accomplish this? Remko Popma On Friday, 29 April 2016, Remko Popma wrote:

Re: Allocation Instrumenter

There's a fork with some activity: https://github.com/malamut2/large-object-watchdog On 3 May 2016 at 19:12, Remko Popma wrote: > Shall we first create a Git pull request that implements the fix to make > it minimum effort for the maintainer to address this? > > Any volunteers? :-) > > Sent from

Re: Allocation Instrumenter

Shall we first create a Git pull request that implements the fix to make it minimum effort for the maintainer to address this? Any volunteers? :-) Sent from my iPhone > On 2016/05/04, at 6:26, Ralph Goers wrote: > > I have no idea what can be done under the apache github account. > > Ralph >

Re: Allocation Instrumenter

I have no idea what can be done under the apache github account. Ralph > On May 3, 2016, at 1:48 PM, Gary Gregory wrote: > > Do we fork it under one of our accounts or the apache github account? > > Gary > > On May 3, 2016 12:02 PM, "Ralph Goers" > wrote: >

Re: Allocation Instrumenter

Do we fork it under one of our accounts or the apache github account? Gary On May 3, 2016 12:02 PM, "Ralph Goers" wrote: > > Guess we have to fork it? > > Ralph > >> On May 3, 2016, at 11:48 AM, Gary Gregory wrote: >> >> Yikes, no reply on https://github.com/google/allocation-instrumenter/issue

Jenkins build became unstable: Log4j 2.x #1923

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Allocation Instrumenter

Guess we have to fork it? Ralph > On May 3, 2016, at 11:48 AM, Gary Gregory wrote: > > Yikes, no reply on > https://github.com/google/allocation-instrumenter/issues/15 > > > G > > On Thu, Apr 28, 2016 at 10:51 AM, Remko Popma

Re: Allocation Instrumenter

Yikes, no reply on https://github.com/google/allocation-instrumenter/issues/15 G On Thu, Apr 28, 2016 at 10:51 AM, Remko Popma wrote: > Hi Colin, > > I'm contacting you because you are listed as one of the contributors to > the allocation-instrumenter >

Jenkins build is back to stable : Log4j 2.x #1922

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Comment Edited] (LOG4J2-1011) Dependencies for layouts should be documentated

[ https://issues.apache.org/jira/browse/LOG4J2-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269075#comment-15269075 ] Remko Popma edited comment on LOG4J2-1011 at 5/3/16 5:02 PM: -

[jira] [Commented] (LOG4J2-1011) Dependencies for layouts should be documentated

[ https://issues.apache.org/jira/browse/LOG4J2-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269075#comment-15269075 ] Remko Popma commented on LOG4J2-1011: - We don't want to leave this open forever thoug

Jenkins build became unstable: Log4j 2.x #1921

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1011) Dependencies for layouts should be documentated

[ https://issues.apache.org/jira/browse/LOG4J2-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268763#comment-15268763 ] Mikael Ståldal commented on LOG4J2-1011: No, but I cannot guarantee that is compl

[jira] [Commented] (LOG4J2-1011) Dependencies for layouts should be documentated

[ https://issues.apache.org/jira/browse/LOG4J2-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268719#comment-15268719 ] Remko Popma commented on LOG4J2-1011: - Okay, I added that. Can you think of anything

[jira] [Commented] (LOG4J2-1011) Dependencies for layouts should be documentated

[ https://issues.apache.org/jira/browse/LOG4J2-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268525#comment-15268525 ] Mikael Ståldal commented on LOG4J2-1011: We list dependencies here: http://loggi

[jira] [Updated] (LOG4J2-1378) WebLookup fails with log4j-web dependency

[ https://issues.apache.org/jira/browse/LOG4J2-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] member sound updated LOG4J2-1378: - Description: I'm using the log4j-web dependency for proper (de)-registration of the log4j2 logge

[jira] [Updated] (LOG4J2-1378) WebLookup fails with log4j-web dependency

[ https://issues.apache.org/jira/browse/LOG4J2-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] member sound updated LOG4J2-1378: - Description: I'm using the log4j-web dependency for proper (de)-registration of the log4j2 logge

[jira] [Created] (LOG4J2-1378) WebLookup fails with log4j-web dependency

member sound created LOG4J2-1378: Summary: WebLookup fails with log4j-web dependency Key: LOG4J2-1378 URL: https://issues.apache.org/jira/browse/LOG4J2-1378 Project: Log4j 2 Issue Type: Bug