Hi, what's the procedure for moving a resolution of this issue forward? The fix in #336 is quite small, and if the maintainers have some feedback, I'd be happy to incorporate it. Notably, the author of #339 seems to have encountered precisely this issue in Dropwizard. Thanks, Mark ---------- Forwarded message --------- From: Mark Elliot <mark.elliot@gmail.com> Date: Fri, Oct 7, 2016 at 4:37 AM Subject: LOGBACK-1189: detect previous copyAttributeMap calls To: <logback-user@qos.ch> Hi, there's a serious functionality bug with logback-access described in LOGBACK-1189 (which also proposes a fix). I pushed a fix here https://github.com/qos-ch/logback/pull/336 <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_qos-2Dch_logback_pull_336&d=DQMGaQ&c=izlc9mHr637UR4lpLEZLFFS3Vn2UXBrZ4tFb6oOnmz8&r=Vp81aOxWZvuVgVK_wp-VF3pIYG92B19LcCw6XKeYC0U&m=QRVzZuRWtoCllqMOXR91q7mQMPe_Ce8VotMpMGWGBPw&s=zEEkWmTtf0-9NIgY30dL40HEqN8NB8dpVdt1tVJFfT4&e=>, and wonder when we might be able to get this merged and released. I suspect http://mailman.qos.ch/pipermail/logback-user/2016-September/004800.html is another (and high profile) manifestation of this problem. Thanks, Mark