[jira] [Closed] (LOG4J2-1388) Upgrade allocation-instrumenter from 3.0 to 3.0.1

2016-05-17 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1388. --- > Upgrade allocation-instrumenter from 3.0 to 3.

[jira] [Resolved] (LOG4J2-1388) Upgrade allocation-instrumenter from 3.0 to 3.0.1

2016-05-17 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1388. - Resolution: Fixed Fixed in master in commit a70ea25. > Upgrade allocation-instrumenter from

[jira] [Created] (LOG4J2-1388) Upgrade allocation-instrumenter from 3.0 to 3.0.1

2016-05-17 Thread Remko Popma (JIRA)
Remko Popma created LOG4J2-1388: --- Summary: Upgrade allocation-instrumenter from 3.0 to 3.0.1 Key: LOG4J2-1388 URL: https://issues.apache.org/jira/browse/LOG4J2-1388 Project: Log4j 2 Issue Type

Fwd: [google/allocation-instrumenter] NullPointerException in other shutdown hooks (#15)

2016-05-16 Thread Remko Popma
FYI > From: Colin Decker > Date: 2016年5月17日 4:09:34 JST > To: google/allocation-instrumenter > > Cc: Remko Popma , Author > Subject: Re: [google/allocation-instrumenter] NullPointerException in other > shutdown hooks (#15) > Reply-To: google/allocation-instrumenter

Re: Allocation Instrumenter

2016-05-04 Thread Remko Popma
Created pull request with the fix that Ami suggested. https://github.com/google/allocation-instrumenter/pull/16 On Wed, May 4, 2016 at 1:22 PM, Ami Fischman wrote: > Replied on public issue. > > On Tue, May 3, 2016 at 7:44 PM Remko Popma wrote: > >> (Added Jeremy Manson a

Re: Allocation Instrumenter

2016-05-03 Thread Remko Popma
(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

Re: Allocation Instrumenter

2016-05-03 Thread Matt Sicker
che 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 rep

Re: Allocation Instrumenter

2016-05-03 Thread Remko Popma
; 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 >> >>

Re: Allocation Instrumenter

2016-05-03 Thread Ralph Goers
ralph.go...@dslextreme.com>> wrote: > > > > Guess we have to fork it? > > > > Ralph > > > >> On May 3, 2016, at 11:48 AM, Gary Gregory >> <mailto:garydgreg...@gmail.com>> wrote: > >> > >> Yikes, no reply on > >

Re: Allocation Instrumenter

2016-05-03 Thread Gary Gregory
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:

Re: Allocation Instrumenter

2016-05-03 Thread Ralph Goers
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 > <https://github.com/google/allocation-instrumenter/issues/15> > > G > > On Thu, Apr

Re: Allocation Instrumenter

2016-05-03 Thread Gary Gregory
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 > <https://githu

Allocation Instrumenter

2016-04-28 Thread Remko Popma
Hi Colin, I'm contacting you because you are listed as one of the contributors to the allocation-instrumenter <https://github.com/google/allocation-instrumenter> project on GitHub. We are working on Log4j 2 <http://logging.apache.org/log4j/2.x/>, and the main theme of the upcomi