From 12151e5c30568680b9e39f192c938f9aa18ba0b5 Mon Sep 17 00:00:00 2001
From: Yurii Rashkovskii <yrashk@idbns.com>
Date: Sun, 27 Apr 2008 08:52:06 +0300
Subject: [PATCH] storage-5 bug appears to be back

---
 bugs/issue-fa64e74e54d1dd7a895939fb8bd41a899fe746ce.yaml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/bugs/issue-fa64e74e54d1dd7a895939fb8bd41a899fe746ce.yaml b/bugs/issue-fa64e74e54d1dd7a895939fb8bd41a899fe746ce.yaml
index df880fab..aef5287a 100644
--- a/bugs/issue-fa64e74e54d1dd7a895939fb8bd41a899fe746ce.yaml
+++ b/bugs/issue-fa64e74e54d1dd7a895939fb8bd41a899fe746ce.yaml
@@ -32,7 +32,7 @@ type: :bugfix
 component: Storage
 release: v0.0.3
 reporter: Yurii Rashkovskii <yrashk@idbns.com>
-status: :closed
+status: :in_progress
 disposition: :fixed
 creation_time: 2008-04-17 21:28:49.887863 Z
 references: []
@@ -55,3 +55,7 @@ log_events:
   - Yurii Rashkovskii <yrashk@idbns.com>
   - closed issue with disposition fixed
   - That appears to be a spec bug (store was not synced, and autosync was trying to sync everything on files already engaged in the next subsequent example)
+- - 2008-04-27 05:51:35.607192 Z
+  - Yurii Rashkovskii <yrashk@idbns.com>
+  - changed status from closed to in_progress
+  - It appears that it still fails sometimes.