hydrusnetwork/hydrus v606-future-01

Version 606 Future 01

on GitHub

Advanced Users Only!

This is a test build of v606. It has:

• PySide6 (Qt) is updated from 6.6.3.1 to 6.7.3 (test version is now 6.8.1.1, which source users on Python 3.13 can run)
• On macOS, PyQt6 (Qt) is updated from 6.6.0 to 6.7.1
• OpenCV (image stuff) is updated from 4.8.1.78 to 4.10.0.84, which lets us update numpy (test version is now 4.11.0.86)
• numpy is switched from <2.0.0 to >=2.0.0. this adds Python 3.13 support to hydrus for source users
• pillow-jxl-plugin is added, and thus we have Jpeg-XL support (thanks to some users for navigating this!)
• the python mpv package is updated from 1.0.6 to 1.0.7 (test verison stays at 1.0.7, there is nothing new)
• twisted (the networking engine that runs the hydrus server and client api) is updated for better TLS and http2 support
• some import hacks that helped PyInstaller bundle old numpy and OpenCV are removed

I do not know if this build will cause dll errors in a specific OS, so before I merge these updates into the normal release, I would like advanced users to simply try it out and see what happens.

So, if you would like to help me out:

• Extract it to your desktop or similar. DO NOT USE IN A REAL CLIENT IN YOUR FIRST ATTEMPT.
• Does it boot?
• If mpv works in your real client, does it still work here?
• How do your images look? Any incorrect colours or static?
• Do you have any UI issues, particularly stuff like menu positioning on a multi-monitor setup?

If it works with no problems and you are feeling brave, please test it on an existing installation so we can see if there are dll merge/overwrite conflicts:

• MAKE A BACKUP. IF YOU CANNOT BACKUP OR ARE UNCERTAIN HOW TO RESTORE, DO NOT DO THIS
• Warning: Do not use the test extract you made earlier on your desktop to update! This extract has a new database in it, and if you were to, say, drag and drop it on your real build, you would overwrite your real database. Update just as you normally would.
• Update exactly as you normally would using the downloaded build file.
• Does it boot ok?

Note that you should not import any jpeg-xl files to your real db in case there are problems and I need to delay the full rollout of this tech. You can try jpeg-xl on the desktop test extract, but not for real, yet!

Let me know via email or discord or post on the release threads. I'd like to know your OS, too!

macOS users have a different situation, where an App will try to use your real release's db location by default, so the testing situation will have to be smarter, probably with a -d launch parameter. If you are a mac user and aren't sure what that means, do not try this!

Thanks!