Added a comment: Found the issue

This commit is contained in:
tim@5431dd39464df207b7d46d3cf1bc74c82123ac68 2022-01-03 08:25:05 +00:00 committed by admin
parent e77ef584cc
commit 4c9bc9e942

View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="tim@5431dd39464df207b7d46d3cf1bc74c82123ac68"
nickname="tim"
avatar="http://cdn.libravatar.org/avatar/967c2815f001d24b5f9f33300c03ba6f"
subject="Found the issue"
date="2022-01-03T08:25:05Z"
content="""
Hi Joey,
Thank you for having a look at this, but we can put this one under \"my own stupidity\". The files that give these errors are apparently only status files which get rewritten every time you play a recording, so they continuously get rewritten, get \"git annex add\"ed with a cron job, but don't always get pushed before they get overwritten, so yeah, it's not unexpected that some of these may get lost at some point.
Still no real data lost though, but errors like these worry me enough to file a bug report.
regards,
Tim
"""]]