/hydrus/ - Hydrus Network

why png
(111.42 KB, 1680x606)

Has this been fixed yet? Last time I asked was over a year ago.
These don't show up in the dupe filter unless I manually disband the dupe group, but how did they obtain it in the first place?
Happens regularly but not that often to be a major nuisance.

I had a good week. I ended up working on technical improvements, fixing some issues with deleted file tracking and exposing multiple maintenance timings for customisation. There is also a variety of optimisation that should slightly de-lag very heavy clients.

The release should be as normal tomorrow.

 >>/1550/
I am sorry, I cannot remember this well. Can you say more what is not working right here? It looks like you have a couple of files set as duplicates, and they are showing up in the search result. Have you never set these as duplicates, and they seem to have spontaneously duped together?

Or do you use the duplicate filter, and have seen files like this, but always set 'and delete the other', and so it is odd that this has happened and they remain in your 'my files'? Is that why there is only one pair when you do this (normally expansive) search?

If it is strange that these files are not showing up in the duplicate filter--that is intentional. The duplicate filter only shows potential duplicate pairs. Once those potentials are processed in the filter, they become like this pair--set as duplicates.

As a side thing, I am planning out a thumbnail expansion to give all thumbnails quick knowledge to all of their current file relationships, which should make some of these menus a bit cleaner and more naturally human (e.g. saying 'these two are duplicates' explicitly, rather than having to infer it from everything else going on). Unfortunately, I have to fetch this data on a per-file basis from the database on every right-click, so I can't do all the calculations I'd like.

 >>/1551/
So I avoided using the dupe filter altogether during all this time to make sure it has nothing to do with it and while the frequency of these weird dupes reduced, they continue to appear. Either way, I never encounter them in the filter before they show up here and I always delete the dupes I find.
These weird dupes differ only in compression as they usually involve an image imported (from API) a long time ago and its copy retrieved recently, probably because the server's compression format being updated. They have multiple image urls, some are matching, others different between the two.

So basically these are images that got assigned the same dupe group without going through the filter where I would have deleted one. Instead I have to look for these stealth dupes in a special search query.

 >>/1558/
Thanks. That's very strange behaviour. As far as I know, the client will only ever apply a duplicate pair relationship if you work through the duplicate filter or apply it manually on a selection of thumbnails, either through that menu or with a shortcut. I have no auto-dupe tech yet.

As a side thing, there is some transitive behaviour, so if A is a dupe of B, and you then set B to be a dupe of C, then A will be duped to C also, but of course this needs the triggering B->C relationship set in the first place, which it sounds like you are not doing. Also, duplicate relationships will survive files being deleted and re-imported, if that could be happening here.

If you can figure out a way to reliably reproduce this situation, or you gather any other information that would help me track this down, please let me know.