@kitterman the bug is triaged but not currently scheduled. This is not because we don't want to fix it but simply because given the finite resources we have and the many bugs we have to tackle, we've had to postpone working on it for a bit. If you, or anyone else, feels like jumping in and helping prepare a branch that solves the problem, we'll be happy to help (and eternally grateful) - find one of us on IRC for a pre-implementation chat. Otherwise, we're definitely going to fix it ourselves soon.
@kitterman the bug is triaged but not currently scheduled. This is not because we don't want to fix it but simply because given the finite resources we have and the many bugs we have to tackle, we've had to postpone working on it for a bit. If you, or anyone else, feels like jumping in and helping prepare a branch that solves the problem, we'll be happy to help (and eternally grateful) - find one of us on IRC for a pre-implementation chat. Otherwise, we're definitely going to fix it ourselves soon.