Comment 1 for bug 1545129

Revision history for this message
Miklos Szel (miklos-szel) wrote :

I can confirm that the issue still persists in the latest stable (2.2.20) and it caused us unexpected data loss.