github hydrusnetwork/hydrus v450
Version 450

latest releases: v599, v598, v597-future-1...
3 years ago

misc

  • when exporting files from the file export window, a cancellable popup job with progress updates is also created. if you close the window, you can still cancel the job from the popup
  • fixed a crash bug in file export window
  • system:num file relationships (duplicates) now correctly only returns files in the current file search domain (previously, it returned all files, including those previously deleted etc...)
  • I rearranged some of the thumbnail menu file relationships actions menu. I'm not really happy with this, but a shuffle is easier than a full rework
  • fixed the '4k' resolution label replacer, which was looking at 2060 height not 2160 by mistake
  • the phash generation routine (part of the duplicates system, happens on image imports) now uses less memory and CPU for images with an alpha channel (pngs and still gifs), and if those images are taller or wider than 1:30 or 30:1, the phashes are also better quality
  • the 'fill in subscription gap' popup button now correctly boots its created downloader when the action also opens a new downloader page. previously, due to overactive safety code, it would hang on 'pending' until a client restart. related similar 'start downloader after creating page' actions off drag and drop or client api should also be more reliable

repositories (also the various improvements in 449-experimental are folded in)

  • fixed an issue with some 'force repository account refresh' code not kicking in immediately
  • when a client sees repository update period change, it now recalculates the metadata next check time
  • fixed a bug with the new repo sync where updates just added from additive sync were not being processed until client restart. related long-term buggy 'do we have this hash in updates?' and 'how many updates are there?' tests for update metadata are also fixed
  • the experimental by-content-type repository reset from last week now leaves pending content in place
  • the reset also now clears cached service info counts for files, tags, and mappings

client api

  • the /get_files/search_files command now takes six new parameters for file/tag domain selection and file sort type and order
  • I wrote out some simple help and added some hacky unit tests for these new parameters. it needs another pass for potential bug fixes and readability/specificity (e.g. what does 'asc' for 'sort by ratio' mean?), but let me know how you get on anyway
  • fixed the new system predicate parsing for system:hash with only one hash
  • improved the url system predicate examples in client api documentation
  • client api version is now 19

mr bones

  • mr bones now reports the correct numbers for your 'my files' again (and will continue to do so as multiple local file services are added)
  • mr bones now reports total files deleted and their total size
  • mr bones now reports your earliest recorded file import time
  • mr bones now has separate tabs for different stats types. this neatly ditches the giant stack of numbers this was becoming, but I may revisit it. some people who take mr bones screens will prefer all the info in one easy shot, while I others I know would rather the 'viewing habits' stuff were not immediately there. maybe expanding boxes?
  • fixed some mr bones layout

boring code cleanup

  • made a new base class for the different database modules to hold cursor and collect common administrative functions
  • all database queries (about 1,200 of them) now go through a single location in the new class
  • a new profile mode, 'query planner' mode, now prints query text and EXPLAIN QUERY PLAN lines to a new profile log. this is a new experimental thing, extremely spammy, but will help with diagnosing very unusually slow queries on individual clients (it'll most likely show up odd sqlite versions, weird data distributions, or un-analysed tables)
  • updated a core function in 'all known files' mappings change autocomplete count adjustment. this seemed to have extremely bad worst case time, and I think it might have been giving some bad counts in unusual situations

Don't miss a new hydrus release

NewReleases is sending notifications on new releases.