diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-12-13 10:49:39 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-12-13 10:49:39 -0400 |
| commit | 4e899b306166533c7b2d6b6ac2dc44dd3453a107 (patch) | |
| tree | 008118bb672ca57ce49d119191b046f4c846ea78 | |
| parent | b159fc00324d6fd0e664b21a8b609ec48f8c7b2d (diff) | |
analysis
| -rw-r--r-- | doc/bugs/Metadata_values_get_stuck_when_repeatedly_modified_in_the_same_batch_mode_run/comment_1_627bb742a5042741e9a1c294addd69b2._comment | 6 |
1 files changed, 6 insertions, 0 deletions
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 8f8447491..9541f1d74 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". """]] |