/hydrus/ - Hydrus Network

Archive for bug reports, feature requests, and other discussion for the hydrus network.

Index Catalog Archive Bottom Refresh
Name
Options
Subject
Message

Max message length: 12000

files

Max file size: 32.00 MB

Total max file size: 50.00 MB

Max files: 5

Supported file types: GIF, JPG, PNG, WebM, OGG, and more

E-mail
Password

(used to delete files and posts)
Misc

Remember to follow the Rules

The backup domains are located at 8chan.se and 8chan.cc. TOR access can be found here, or you can access the TOR portal from the clearnet at Redchannit 3.0.

US Election Thread

8chan.moe is a hobby project with no affiliation whatsoever to the administration of any other "8chan" site, past or present.
(4.03 KB 480x360 u9lowRlI0EQ.jpg)

Version 353 hydrus_dev 05/22/2019 (Wed) 23:05:25 Id: e175d6 No. 12669
https://www.youtube.com/watch?v=u9lowRlI0EQ windows zip: https://github.com/hydrusnetwork/hydrus/releases/download/v353/Hydrus.Network.353.-.Windows.-.Extract.only.zip exe: https://github.com/hydrusnetwork/hydrus/releases/download/v353/Hydrus.Network.353.-.Windows.-.Installer.exe os x app: https://github.com/hydrusnetwork/hydrus/releases/download/v353/Hydrus.Network.353.-.OS.X.-.App.dmg linux tar.gz: https://github.com/hydrusnetwork/hydrus/releases/download/v353/Hydrus.Network.353.-.Linux.-.Executable.tar.gz source tar.gz: https://github.com/hydrusnetwork/hydrus/archive/v353.tar.gz I had a great week. I finished the basics of the new file maintenance system I wanted, cleaned up the duplicate filter a little more, and fixed a bunch of bugs. file maintenance system There are a number of large file re-checking jobs the client wants to do, both now and in the future. Going back to figure out more accurate video durations and image rotations, discovering webms that were formerly incorrectly detected as mkvs, eventually integrating videos into the duplicate checking system, all of these will require a combined whack of maintenance CPU that I don't want to hit all at once. I have previously sketched out some disparate systems for these jobs, but none were really doing the trick, so this week I unified it all into one nice system that can handle all sorts of jobs. This new system is simple for now but will get more work in future. You do not have to do anything, but if you pay attention to your maintenance work, you may notice some new file metadata and thumbnail jobs running in the background or on shutdown. This new system fits into normal maintenance just like database analyzing or repository processing. You can govern whether it is permitted to run in regular idle time and/or shutdown time under options->maintenance and processing and also change its in-built 'throttle', which limits the number of files it will work on (rather than running full bore on what in future may be quite large jobs). The default throttle is 200 files every day, which for most jobs on most machines will be about 30 seconds to three minutes work. Do not expect it to do much work yet. Existing file regeneration routines now work through this system, and it does its job much better than before. If you hit right-click->regenerate->x on some thumbnails, the job now runs in a regular popup button (rather than the locking 'modal' one from before), letting you keep browsing while it works. And if you select more than 50 thumbnails (think, say, right-clicking on 2,000 video files and saying to regenerate their thumbnails if they are the wrong size), you will now get the option to schedule that big job for later, at which point those 2,000 jobs will end up in the normal idle maintenance queue, to work at 200 files a day or whatever you wish. This system is fairly opaque at the moment. You can trigger it with the thumbnail right-click, and certain db operations may schedule new jobs for it, but there is no UI to review it yet. In the coming weeks, I expect to write a new 'review' window off the database menu that will let you review total pending jobs, start work manually, and add and remove pending jobs en masse through the regular search interface. I'll slowly integrate more of the client into it as well, letting it add more jobs into the queue by itself. Let me know how this all works for you! duplicate filter The duplicate filter interface got some more work this week, particularly in cleaning up some of my original version's over-engineering. The actions you can choose on the right panel are now split more clearly into 'yes, these files are duplicates, and here is how' decisions vs the 'alternates' and 'not dupes' decisions. Also, 'this file is better' is now split into two buttons for 'delete the worse file' and 'keep both'. This 'delete or not' is split at the shortcut level into two actions as well, if you wish to map both. Existing shortcuts (left-click by default in the filter) will update to the 'and delete the worse file' version. The complicated 'duplicate action options' object (which governs how to merge metadata across duplicates) therefore no longer handles file deletion. It is also now only attached to the 'better/worse' and 'files are the same' actions–we never found a good reason to merge metadata across all alternates or 'not duplicates', so I have removed it completely. If you want a complicated file delete action, hitting the 'custom action' button now asks you if you wish to delete the file you are looking at, the other one, or both. Also, to reduce confusion with alternates–which are also technically not duplicates–'not duplicates' is now renamed across the program to the more precise 'not related/false positive'. The 'false positive' action is a record in the db saying 'despite the similar files search thinking these files were related, it was incorrect, so do not bring it up again'. My hope is that filtering is a bit faster here. If two duplicate files are of very different quality, it is still easy to delete the bad one, but if they are more close and you want to keep both, it is now just one click. As for the big db-level rewrite, I prepped the duplicate db code for it this week. I am standing at the cliff-edge and feel great about jumping off, so next week I hope to get started on the new code properly and migrate one or both of the current 'alternates' and 'false positive' data to the new system. the rest I fixed an issue with the recent 'collect by' session saving where the accompanying sort was not being renewed on a session load. Also, several problems with collected media and sort by 'approx bitrate' are fixed. There's a new checkbox under options->sort/collect that makes it so the default sort is updated every time you click a new sort in regular browsing. It sounds a pain but is actually pretty neat! The 'all local files' domain is now hidden from view in new page selection and the tag autocomplete dropdown if you are not in advanced mode. This domain, which is fairly technical and covers both trash and 'my files' and the sometimes-hidden repository update files, is often confusing to new users and is rarely useful even for people who know what it does. If you use the client's local booru and need to override its host when you copy an external link, this option has moved from options->connection to the local booru's manage services panel. You can also override scheme and port as well! The old host override option is gone completely, and the only other place it was used, the manage upnp dialog, now fetches this info more efficiently and fails more gracefully. full list
[Expand Post] - duplicate filter: - duplicate action options no longer handle file deletion - renamed 'not duplicates' across the program to 'not related' or 'false positive' - 'alternates' and 'not related/false positive' duplicate actions no longer have duplicate action options. no merge content update now occurs on these actions - the duplicate filter hover panel now splits 'this is better' decisions into two buttons–whether to delete or keep the worse file - when selecting 'custom action' in the duplicate filter hover panel, it now asks if you would like to delete the current file, the other file, or both - the 'duplicate_filter_this_is_better' shortcut action will be auto-updated to 'duplicate_filter_this_is_better_and_delete_other'. an alternate 'duplicate_filter_this_is_better_but_keep_both' is now also available - the 'duplicate_filter_not_dupes' shortcut action will be auto-updated to 'duplicate_filter_false_positive' - separated the buttons on the duplicate filter hover panel to more carefully split 'yes, files are duplicates' vs other decisions - in prep for the duplicate db overhaul, refactored all PHash search code and Duplicate management code apart - misc other prep work for duplicate db overhaul - . - file maintenance: - wrote a new unified manager to handle various long-term file maintenance tasks like regenerating file metadata and thumbnails - options to govern how this manager can run are now in options->maintenance and processing. you can enable it for idle and shutdown maintenance time and give it a throttle to limit how fast it will work on files, defaulting to 200 per day - unified the previous db-level attempts at file maintenance to the new system, which supports async job queueing, and moving regen code up to the new manager, out of the db lock - unified a variety of file and thumbnail regen code to work through the new simpler and saner path - the right-click->regen thumbnail commands now run through the new manager and no longer need a modal popup. you can keep browsing while they work. they will also not hang the ui as the old system could on big jobs - when right-click->regenning on more than 50 thumbnails, you now get a dialog asking if you want to do the job now or put it off later - file maintenance tasks can now run in shutdown time! you will get previews of the jobs with file counts and status progress reports on the shutdown splash - cleaned up some file extension renaming and dupe-removing code - in future, I will move the current file integrity check to this new system and have some ui to prompt and set up other big jobs, like fixing various historical misparsing issues - thumbnail resizing during thumbnail fade that resizes down is now more efficient - moved the ClientFilesManager to ClientFiles.py - . - the rest: - the 'manage upnp' dialog now moves the duplicated external ip display from the column up to the status text at the top. it fetches the ip after the initial mappings fetch is done. this ip is no longer affected by the external host override option - cleaned up options->connection page and removed the now defunct external host override option - the manage services page for the local booru now has optional override for scheme, host, and port for the 'copy external url' function - fixed an issue with the recent 'collect by' session saving where a restored session that needed a collect was not sorted - fixed an issue with collections being sorted by approx bitrate - added a new checkbox to options->sort/collect to set it so the default sort updates every time you choose a new sort anywhere - fixed an issue with 'remove trashed files from view', which was incorrectly removing on 'all local files' pages - the 'all local files' file domain, which is frequently confusing to new users, is now no longer an option for new file pages or the autocomplete file domain if the user is not in advanced mode - the client now searches for versions of urls both with and without a final '/' character when looking up file url import status at the db level and in import lists. system:known_url is unfortunately still an inefficient mess - improved how the server code deals with some connectionLost errors - cleaned up and unified some older dialog button code - fixed a problem in manage tag siblings when petitioning existing pairs and then cancelling when asked for a reason - fixed a miscount issue when uploading pending tags while many new tags are coming in. progress would sometimes be -754/1,234, ha ha - db maintenance, repository sync, and file maintenance processing will all now wake on a force idle mode call - deleted some old code - misc fixes and cleanup - some misc gui layout fixes next week I have quite a few smaller jobs waiting for me, so other than the new duplicate db tables, that's top priority. Some UI bugs to deal with, maybe some Client API work, an experimental jpeg quality estimator, possibly support for some new filetypes, and hopefully a fun new way to quickly add very complicated OR search predicates thanks to a clever user's work. Just a note, E3 is coming up soon and I will take my shitposting vacation week for it as usual. I think it'll be 356 that's delayed a week.
Anonymous 05/23/2019 (Thu) 01:27:48 Id: c9c96c No. 12670
You're a saint, thank you for all the work that you do.
Anonymous 05/24/2019 (Fri) 09:32:34 Id: e7d82c No. 12683
>>12637 Send file right 1 tab… this actually would be helpful, if you could get a string of those for right 1 right 2 so on so forth a fairly large sort could happen without a need for exact names. as for if you could send files to named tabs… limit it to within that level of tabs. take for example how I am doing the 10+mb sort I have one top level page of page then I have 4 page of pages below that gif - application - image - video and under each of those I have various reasons I want to delete or save along with delineations like images, I sorted out all the images that were stupidly tall from here you got either making new tab and putting the images in there with a static name, or you could make the hotkeys static but a right click on the tab and telling it which hotkey it is, so every tab in that level of page of page (or top level) will move the file accordingly. but like I said, a simple move image right X would also be effective, the only downside would be every tab on the page of page, the hotkeys would have a different effect.
Anonymous 05/24/2019 (Fri) 14:02:17 Id: 313ccb No. 12685
Is there a way I can override the port so that it doesn't show the colon followed by port number in the url at all? I'm using some proxy and rewriting doohickies to forward external requests and I hope to not have to specify the port number. I'm currently getting: https://mydomain.moe/booru:/gallery?share_key=fgsfds (I eventually want to move it to https://booru.mydomain.moe/gallery?share_key=fgsfds but I'm having trouble with the https config in nginx.)
Anonymous 05/24/2019 (Fri) 14:18:55 Id: 313ccb No. 12686
>>12685 So I patched it up by setting the port override to 443/booru It's a little funky, but it works for now.
Anonymous 05/25/2019 (Sat) 06:14:43 Id: 32419d No. 12694
(68.29 KB 519x444 Untitled.png)

There is no tag copying on alts anymore? It's gone from the menu. I found it useful to transfer some less specific tags like creator, series and character between alts.
Anonymous 05/25/2019 (Sat) 08:10:53 Id: 32419d No. 12695
(26.08 KB 486x231 Untitled.png)

It happened again, a week left of the month
Anonymous 05/25/2019 (Sat) 13:43:55 Id: b7656c No. 12701
(2.48 KB 266x105 ClipboardImage.png)

>>12695 Getting the same error. Services menu says I sent a million requests worth 256GB in total. I'm pretty sure I didn't use it nearly as much as that.
hydrus_dev Board Owner 05/25/2019 (Sat) 22:17:15 Id: e175d6 No. 12710
>>12670 Thanks m8, I am really glad you like it. I'll suggest you don't think me a hero though–I'm a typical Anon, and I'll only disappoint you. >>12685 >>12686 Shit, sure, I'll make it so if you put in an empty-but-not-none value for that, it doesn't put the colon in. I can do this this week with 99.7% certainty.
hydrus_dev Board Owner 05/25/2019 (Sat) 22:22:06 Id: e175d6 No. 12711
>>12694 Yes, for now I have reduced it to content merge only on positive 'yes these are dupes' relationships. When I ultimately do do alternates and a workflow to process them further, I expect to have labels or types to go with each relationship, like, say, 'WIP' (work in progress) or 'based on original work'. Some of those types would have approprate content merge rules, others (mostly meme derivations) would not. I'll revisit the problem then. I fully expect to make the content merge apply retroactively, so I hope we can fix any gaps here, and more intelligently, later on.
hydrus_dev Board Owner 05/25/2019 (Sat) 22:24:59 Id: e175d6 No. 12712
>>12695 >>12701 Yeah, it is the shared account that everyone uses. This happened last month as well. I set a 256GB/month limit some years ago, and we have finally grown to hit it. Once I am done with this duplicate work, probably 6-8 weeks or so, I hope to tackle this fundamental problem of update distribution with tag repositories (and do some other work as well to help you better filter what tags you actually want from the PTR). It'll ease up again on the 1st June, and we'll see when (fingers crossed for if) we hit the limit again.
hydrus_dev Board Owner 05/25/2019 (Sat) 22:28:19 Id: e175d6 No. 12713
>>12683 Ok, thanks. I'll give 'move left/right one' and 'move to first/last' a go, which gives you four options, and we'll see how that works out.
Anonymous 05/26/2019 (Sun) 17:12:50 Id: 313ccb No. 12720
>>12710 Contrary to your opinion, and in agreement with previous anon, you are indeed a saint.
Anonymous 05/28/2019 (Tue) 22:47:43 Id: e7d82c No. 12747
>>12713 Move left, move right, move first, move last on the video tab I have stupidly large remove convert down not hydrus view again and decide with check before remove music video in for good measure the first set is a wide range of reasons for a quick cull, the second set a second pass, with move left and right, I could easily set it up so its in between 2 tabs and move it to a second for more… hell, even a worst case scenario I could have multiple page of pages and filter that way. not as set and forget as proper defined hotkeys, but should greatly increase the rate of sorting because I don't have to move them with the mouse anymore. definitely will be a god send once i'm out of video land.
Anonymous 05/29/2019 (Wed) 19:36:40 Id: e7d82c No. 12753
Ill post this again in the new thread too, I decided that the converted down images will get will get a rating of Converted Down/Keep Large with 2 stars and not selectable as an option it allows files to either be converted down and hidden from a search, or specifically keep the large file and hide it, also removed all files from the archive, everything needs a filter pass. these images that were converted down were interesting enough for me to keep/convert down but not really sure if I will long term storage them or not. when I en mass rated them to converted down I got that error InterfaceError Error binding parameter 0 - probably unsupported type. Traceback (most recent call last): File "include\HydrusDB.py", line 561, in _ProcessJob result = self._Write( action, *args, **kwargs ) File "include\ClientDB.py", line 12905, in _Write elif action == 'save_options': self._SaveOptions( *args, **kwargs ) File "include\ClientDB.py", line 10112, in _SaveOptions self._c.execute( 'UPDATE options SET options = ?;', ( options, ) ) sqlite3.InterfaceError: Error binding parameter 0 - probably unsupported type. It doesn't seem to have made anything not work, everything's rated, so not sure what it is.
hydrus_dev Board Owner 06/03/2019 (Mon) 18:14:03 Id: e175d6 No. 12847
>>12753 Thank you for this report. This is an odd error–the problem here is that the options object is not being serialised into the db correctly. This is the kind of error I see when someone has like a 2GB subscription, and SQLite falls over trying to make a buffer big enough for it. The options object there is a small thing, automatically saved at various points. Perhaps it was being nullified in some way, or some invalid data was being added to it. I can't think immediately why it would be affected by a rating set event. Can you say more about this rating conversion? You had a 2-star rating service as set up as under manage services, and then when you did a giant ctrl+a->f4->set rating->ok, it took a moment to write that and then popped up this error right at that time? Had you set any other options recently, either in file->options or via one of the 'cog' menu buttons? Anything related to default sort based on that new(?) rating service?
Index Catalog Archive Top Reply
1
Forms
Delete
Report
Quick Reply