/hydrus/ - Hydrus Network

- a user came up with a clever idea to efficiently target regenerations for the recent fix to pixel duplicate calculations for images with opaque alpha channels, so this week I will queue up some pixel hash regeneration. it does not fix every file with an opaque alpha channel, but it should help out. it also shouldn't take _all_ that long to clear this queue out. lastly, I renamed that file maintenance job from 'calculate file pixel hash' to 'regenerate pixel duplicate data'
- the various duplicate system actions on thumbnails now specify the number of files being acted on in the yes/no dialog
- fixed a bug when searching in complicated multi-file-service domains on a client that has been on for a long time (some data used here was being reset in regular db maintenance)
- fixed a bug where for very unlucky byte sizes, for instance 188213746, the client was flipping between two different output values (e.g. 179MB/180MB) on subsequent calls (issue #1068)
- after some user profiles and experimental testing, rebalanced some optimisations in sibling and parent calculation. fingers crossed, some larger sibling groups with worst-case numbers should calculate more efficiently
- if sibling/parent calculation hits a heavy bump and takes a really long time to do a job during 'normal' time, the whole system now takes a much longer break (half an hour) before continuing
- .
- boring stuff:
- the delete dialog has basic multiple local file service support ready for that expansion. it no longer refers to the old static 'my files' service identifier. I think it will need some user-friendly more polish once that feature is in
- the 'migrate tags' dialog's file service filtering now supports n local file services, and 'all local files'
- updated the build scripts to force windows server 2019 (and macos-11). github is rolling out windows 2022 as the new latest, and there's a couple of things to iron out first on our end. this is probably going to happen this year though, along with Qt6 and python 3.9, which will all mean end of life for windows 7 in our built hydrus release
- removed the spare platform-specific github workflow scripts from the static folder--I wanted these as a sort of backup, but they never proved useful and needed to be synced on all changes

next week

More like this, I think, and some general code cleanup.

Anyone here know what's wrong with my Hydrus Companion?
Sending tabs from Gelbooru it says it sends them successfully, but Hydrus says 400 Unknown Error.

Hey, I finally moved to new programming software this week (WingIDE to PyCharm). It was a little jarring dealing with new UI and shortcuts and a billion new settings, so I mostly stuck to simple code cleanup to get to grips with it. I don't have much exciting in my changelog beyond a tweak to system:hash, so rather than put out a thin build tomorrow, I will do some more work instead and move the release on a week.

If you haven't seen it, though, please check out the new help a user put together: https://hydrusnetwork.github.io/hydrus/

It has nice features like search and tables of contents and will be easier to edit in future. 475 will have it too for the local copy and should be out on the 2nd of March.

 >>/1235/
If you check your 'client - date.log' file in the install_dir/db folder, and go to the bottom and look for the timestamp when this happened (and maybe ctrl+f for "400" or "unknown error", whatever text you have), can you see any 'traceback' information for the errors here? Can you clip and pastebin them or just post here? That will show more information on what is actually failing here.

If you are getting popups in the client UI, it should let you just copy the traceback there, too.

 >>/1236/
I go to the hydrus page by typing hy and then enter. going there it's nicer than it was before. however it took quite a while for me to find the links to the various places hydrus is, would it be possible to copy at least the downloads and links to the places you make update posts to the homepage?

 >>/1237/
Thank you, yes, I will. When we collapsed it down a level, the old index with the links go removed. I'll add something back in.

I had a good couple of weeks. I updated my behind the scenes environment and cleared out a wide variety of misc work--bug fixes and little improvements. The built release will also get a local copy of the nice new help a user put together.

The release should be as normal tomorrow.