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 <[email protected]> wrote:
> 
> I have no idea what can be done under the apache github account.
> 
> Ralph
> 
>> On May 3, 2016, at 1:48 PM, Gary Gregory <[email protected]> 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" <[email protected]> wrote:
>> >
>> > Guess we have to fork it?
>> >
>> > Ralph
>> >
>> >> On May 3, 2016, at 11:48 AM, Gary Gregory <[email protected]> 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 <[email protected]> 
>> >> wrote:
>> >>>
>> >>> Hi Colin,
>> >>>
>> >>> I'm contacting you because you are listed as one of the contributors to 
>> >>> the allocation-instrumenter project on GitHub.
>> >>>
>> >>> We are working on Log4j 2, and the main theme of the upcoming 2.6 
>> >>> release is making Log4j 2 garbage-free in steady state running.
>> >>> We use the allocation instrumenter in our JUnit tests to verify that 
>> >>> things are working as expected.
>> >>>
>> >>> However, on our build server we see our test fail spuriously.
>> >>> I believe this is a bug in AllocationRecorder (to do with accessing a 
>> >>> volatile field that has been nulled out by a shutdown hook, details 
>> >>> here).
>> >>>
>> >>> Could you please take a look?
>> >>> If you no longer maintain this project, can you point us to the person 
>> >>> who does?
>> >>>
>> >>> Many thanks!
>> >>> Remko Popma
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >> -- 
>> >> E-Mail: [email protected] | [email protected] 
>> >> Java Persistence with Hibernate, Second Edition
>> >> JUnit in Action, Second Edition
>> >> Spring Batch in Action
>> >> Blog: http://garygregory.wordpress.com 
>> >> Home: http://garygregory.com/
>> >> Tweet! http://twitter.com/GaryGregory
>> >
>> >
>> 
> 

Reply via email to