>>17105
Sure, I'll see what I can do.
>>17106
Thanks, sounds like you are all fine.
I did some testing on my IRL client, which is getting these errors more than my dev situation, and I am confident now that my 'detect when mpv is going crazy' hook is catching false positives on some file loads. I think some file loads are fucking the mpv mainloop somehow, probably bad thread scheduling or choking by the system for whatever reason, maybe even I/O related, but it is ultimately nothing to panic over since it calms down in, idk, 500ms or something?
I'm going to alter my error hook to check for if the file was recently loaded and have a grace period where it'll just endure the issue. Fingers crossed we can still catch the real problems but just have a bit of judder otherwise. Let me know if things get better/worse in future!
>>17127
>Unrelated, but is there a way to display images with tags that won't pass a PTR filter?
Can you explain this more? There is a filter on the PTR that excludes some tags like 'tagme' and 'character request', which are booru things we don't need--is this what you mean? If you want to add tags the PTR won't allow, you'd be looking at adding them to a 'local tag service', which is just on your hard drive and is a place where you have full control. You should already have 'my tags' and 'downloader tags' in a default install, but you can create more if you like under
services->manage services.
When you search for files in hydrus, the 'tag domain' is usually, by default, 'all known tags'. This is basically the union of all your tag services, so if you have 'clothing:thigh-highs' on your local 'clothing' tag service, it'll show up there when you type.
If you are feeling very clever, there are also ways with the tag sibling system that can rename PTR tags on your client.
Let me know if I've misunderstood what you want to do.
>>17128
>>17129
>>17145
Thank you for this report, and I'm sorry for the trouble. You've already done the first thing I was going to suggest--pausing your import folders. I think you are correct that there's some difficult issue with the complicated multi-nested folder structure. I recently altered how import folders do 'ok that path was (result), now lets do (action)', which does all the stuff in 'if file was already in db, then (delete it)' stuff you see in the edit panel. I wonder if that is handling things wrong, or, let's say, failing due to a long filename or something and then working on the same file again and getting into an awful loop and eating up memory and dying.
Can you tell me what your actions are for the import folder here? Is it moving files, ignoring them, deleting? Also, if you look in the edit panel, there should be a 'file log' button. Open up the file log--is every single item actioned, or is there, say, one weird unicode filename or something that is blank? If it all looks good (or it is all empty, say), then depending on your workflow, could you identify what would be in the subsequent sync? What folder(s) would it be actioning next?
Also, can you check your 'client - date.log' in install_dir/db? There may be a whole ton of python 'arghhh running out of memory, super loop recursion hell' tracebacks or something that may shine a light on which part is failing.
Either way, I'll dive into this code this week and tighten up the error handling. I'll bet it is me going 'ok that's done, now the next' in a situation where the original wasn't done correctly, so it is looping.
>>17131
Yeah sorry for the trouble here. We want to enable this eventually, it has been like a twelve year saga to finally allow pixiv ugoira downloads.
Thanks to the work of a user, as of last year we finally have native ugoira support in hydrus. An Ugoira zip will now import, be recognised, and render in client, and if it has timing information either as a json file in the zip or encoded as a note with a particular name, hydrus will obey that timing data. Otherwise it defaults to something reasonable, I think 12 or 25fps.
The problem with downloading them from pixiv is Ugoira is typically presented in a split format, where you have the images and then the timing data is separate, but hydrus only understands files as atomic single objects. Sometimes the images are in a zip and the timing data in a json or js, sometimes the images are loaded dynamically with javascript from an esoteric CDN using embedded ms timings in the js. It is a fucking mess. I'm not sure what Pixiv currently provide, but we are thinking about writing a hardcoded hook for the hydrus downloader to say 'hey, when you have this Pixiv Ugoira URL, you need to get the images and then pull this timing data and zip it all up yourself in a temp dir, and then
that's the file you want to import.
Once we have a nice solution, I can finally undo the veto and we can get nice Ugoiras from the primary source with good timing data.