John Goerzen Thu, 12 Nov 2015 10:27:28 -0800
Hello, I believe that the original patch caused #366560. Perhaps the fix for #366560 broke this; could you send a new patch atop the current version?
Thanks, John
