From e08761288d3a200a4983f9f6c3e5fdb2a8c7a39b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 13 Dec 2016 10:49:39 -0400 Subject: [PATCH] analysis --- .../comment_1_627bb742a5042741e9a1c294addd69b2._comment | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment b/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment index 8f84474915..9541f1d744 100644 --- a/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment +++ b/doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment @@ -13,4 +13,10 @@ it is: That is supposed to unset c, with the CurrentlySet False, but instead c remains set somehow. + +Aha, the use of `addMetaData'` causes the bug. That reuses the same +timestamp, and indeed the same timestamp is used for all the batch +changes. With the same timestamp for the log line that sets c as the line +that removes it, it's indeterminite which line will be acted on first, and +so the removal can be processed before the addition, leaving c "stuck". """]] -- 2.30.2