Public tag repo keeps importing update 1129

Name
Email
Subject
Comment *
File	Select/drop/paste files here
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Embed	(replaces files and can be used instead)
Options	Do not bump (you can also write sage in the email field) Spoiler images (this replaces the thumbnails of your images with question marks)
Password	(For file and post deletion.)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, swf, pdf Max filesize is 8 MB. Max image dimensions are 10000 x 10000. You may upload 1 per post.

File: 1436309599440.jpg (56.33 KB, 500x509, 500:509, Capture.JPG)

Public tag repo keeps importing update 1129 Anonymous 07/07/15 (Tue) 22:53:19 No.917

The public tag repo keeps applying every update since 1129 every time it checks itself. I deleted the update cache files but it's still trying to apply them.

hydrus_dev ## Board Owner 07/08/15 (Wed) 02:08:43 No.920

File: 1436321323219.jpg (154.38 KB, 1223x1008, 1223:1008, a381f31a0cf744bfa9aec41182….jpg)

Thank you for this report. Did it start looping before you deleted the update files, or after? Did it ever get to update 1130?

To stop the errors keep coming up, please pause your repo sync (services->pause->repo sync) for now.

Anonymous 07/08/15 (Wed) 16:43:47 No.922

>>920

Before. It supposedly applied every update up through 1131 and claimed it was finished, but the next day it started with 1129 again and updated through 1132, which is when I realized there was a problem and deleted the update cache.

Anonymous 07/12/15 (Sun) 13:41:18 No.928

File: 1436708478828.jpg (1.22 MB, 2700x1800, 3:2, 5SZjOCv.jpg)

This issue stopped happening. I don't know if you changed anything or not, but I copied the update cache from another Hydrus client I have and updated to the latest version, and it's updating normally now.

hydrus_dev ## Board Owner 07/12/15 (Sun) 17:21:41 No.931

File: 1436721701550.jpg (187.94 KB, 1228x1913, 1228:1913, 704e9e45c262e437d3741f73ea….jpg)

>>928

Great! I speculatively tried something last week, and I think it fixed it. In certain cases, the database copy of the service wasn't getting its notifications (like "We are synced up to 1130") saved to hdd. I made sure it would, which also seems to have fixed an issue where certain bandwidth use tracking was becoming unsynced clientside.

Thank you for this report. I wasn't sure of the nature of this problem until you posted about it.