/hydrus/ - Hydrus Network

While importing files I get the following for each file:

Traceback (most recent call last):
  File "/home/user/Downloads/hydrus-276/include/ClientImporting.py", line 4440, in _WorkOnFiles
    ( status, hash ) = HG.client_controller.client_files_manager.ImportFile( file_import_job )
  File "/home/user/Downloads/hydrus-276/include/ClientCaches.py", line 982, in ImportFile
    file_import_job.GenerateInfo()
  File "/home/user/Downloads/hydrus-276/include/ClientImporting.py", line 375, in GenerateInfo
    if HydrusImageHandling.IsDecompressionBomb( self._temp_path ):
  File "/home/user/Downloads/hydrus-276/include/HydrusImageHandling.py", line 250, in IsDecompressionBomb
    warnings.simplefilter( 'error', PILImage.DecompressionBombWarning )
AttributeError: 'module' object has no attribute 'DecompressionBombWarning'

Same error prevented hydrus from starting, workaround is to comment out line 18 in HydrusImageHandling.py.

>>6876

>The client now recognises .zip, .rar, and .7z files.

Does this mean I can go ahead and import zipped ugoiras?

>the client will now by default detect and not import decompression bombs before they blast your computer. an option to allow them nonetheless is under options->media

Thank you Dev, I was the one with this issue.

Surgery + inability to really do much beside lay down kind + prep for the surgery kind of kept me from making a comment last update so i'll just copy paste what I was writing here, also modifying it a bit as things changed.

~~~~~~

Ok with the new thread watcher, I think the timeings are a bit tight for default.

Easy enough to manually change,

The at last check dialogue is a bit… off, instead of reporting its last check it reports for me 'found 225 files in the last 56 days'…

fuck me the thread is 56 days old, kind of why I would love to see threadwatch able to handle more then 1 thread at a time. give there are quite a few boards I would like to have threads watched in but only have so many resources for watchers before the program borks.

I can't really put it through its paces till /b/ has some threads I want to save, and because of how it looks at files, i'm not really able to test it on other boards so if this isn't how it works disregard it. the recheck time can't double. go up in increments sure, but if it doubles there will be a point where it hits 12 minutes, doubles to 24 someone posts an image right after the 12 minute mark but tread life on a board is only 16-20 minutes, so the file is lost. I like the idea of it, but would also like to see user inputted parameters on a per board basis, as boards like /b/ are kind of special cases where I would realistically want to limit the longest check counter to 7-10 minutes but other boards like hr/ic/3 I would like longer check times.

with that said, there has been an… annoyance that has been creeping up on my a lot recently. in a thread watcher/download page, the first thing scroll is tied too is the sort by option. Personally, when I am in a thread watcher/ download tab, I would like to have it sort by when it tried to import. The closest thing to that is time imported, but several threads have 100 images downloaded 70~ already in db. So is there a way to add a sort by time discovered? as in sort according to when the program tried to import it from said links?

~~~~

Ok thats what I had gotten up to last time before all of the prep work and I need to get X done before I go in happened.

For this release, it appears that either the way thread watcher work or the new thread watcher change the title system has broken previous thread watchers so they no longer know if a thread has 404'ed, I am looking into this to see if it's a recurring problem or just one with older thread watchers from when the switch happened/this came up.

With parsing subjects, this is great, at least till you run into threads that don't use subjects, possibly whole boards that don't use subjects.

So having an option to fall back on [Site][board] for a thread watcher would be helpful this way you would get a tab name that says "4chan - High resolution"

I should also mention with this I can see a point where enough shit gets put on the tab names that it becomes a problem for sorting more so then helpful, so an option to have "Watcher" at the end of the tabs name by default would be helpful.

With the new change to thread watchers being able to change, if there was a way to change the texts color to get attention, like green for a new file or red for 404 to get your attention that would be fantastic.

on a side note I ran into a thread on /b/ the thread checker wants to check again in 1 hour 30 minutes where the oldest thread is as of right now 40~ minutes old with a post.

This program should be able to see what board/page its on, a user definable clap on check times would solve this issue if it was able to be implemented per board.

The issue is also solvable if you are able to check the last thread on pages 10-15's last post and see how long the oldest post lasts and make a custom clamp and let math decided the ramp up form that though I have no fucking clue if that's possible at all, as it stands i'm likely going to change it from 24 hours down to 1 hour per check with a year long wait to see if images post as default and then per thread on fast boards put them down to 3-10 minutes in between checks.

Now just because I went through importing things recently I had a thought… Do I need import folders to be checked?

I mean yes, having the import folder there and set up is nice/important, but do I need it to be checked when im not useing it?

A toggle on import folders to active or inactive would be nice

the use case for me is I download single images that I import once a day, but I also have an import folder for dumping an entire artist archive at once which I want to be checked asap when i'm doing imports like that, but aside from then do I really need the import option always checking?

Body was too long so here is part 2 to >>6880

and with

>>6859

Thanks for looking into it, honestly so long as its not selecting images that are effectively off page i'm ok with nearly any solution you can come up with. The best way I can think of is how acdsee handles it. I can make a video of it sometime later.

------

Just as a side note, seeing as i keep hitting the 145+ mark due to thread watchers alone, I would love to see a multi thread watcher tab. I am sure I have said it before, but everything needed is there with download page of images to do it, all you need is a recheck timer and instead of discarding threads, it keeps them in program and puts it in a queue after import.

This has 2 benefits.

1) the ability to use a pseudo thread watcher on currently unsupported sites

2) the consolidation of thread watchers to one area so tabs are kept to a minimum.

with a few disadvantages

1) a large amount of images, an entire board of images if you like the content of said board could leave a single tab with 37000 images if every thread reached cap and cap was 250 images, but this is a worst case scenerio

2) far less fine control, unless you went in getting the thread watcher to stop when just 1 thread 404'ed would be an issue.

This wouldn't end my use of thread watchers, as there are threads I want to specifically pay attention to, or said board has so few threads on it a mass thread watcher is pointless/overkill.

let me put a specific here. there are currently 50 threads on /hr/ on 4chan I would like all the images from and that's just one board, the newest post on the oldest thread is 7 days old, so that would mean that I would have to keep 50 thread watchers open and going for at least 7 days on a board where I beleive they kept a thread going for nearly 2 years at one point.

Contrast that with something like /b/ where there are 8 threads I would like to pay attention too and the half life almost guarantees the threads will be dead within a 3 hour period of time, or even hr again where 45 of the threads I just want the images, don't care to much about paying attention to the threads on their own as threads, but I do care about 5 of them being thing I want to pay attention to as they come in.

I honestly think a 'little' work would make this a very useful feature... I say little because I have no fucking clue how much work goes on behind it.

Personally, I would have this

- threads stay in the system and re import on X time frame

- threads get a tab like "detailed file imports" so you can see when they 404 or the like and remove them that way if not a system to soft take them out of the import rotation

and that's about it for basic functionality anything more advanced while appreciated would not be necessary.

Ok, just got through a few /b/ threads

For some reason, a thread that hits a literal 404 page isn't coming back as dead/404 but another thread that only hit image and bump caps but is still on the /e/ board is coming back as dead

The most I get out of it is thread paused, the old thread watcher, would at least have a 'how many more checks do you want to make and because I had it set to 60000~ something and check hourly, when a thread would 404, it would at least change the number to 0 and when I hit recheck it would tell me thread 404

I have a few to many tabs open right now to go into the options, will see if something is enabled or disabled once I can get into it.

Hey dev, been away for some months, just now updated and opened Hydrus again, thanks for all your hard work! Really love the pages of pages and drag-and-drop support, and the thread status monitoring will really come in handy.

>>6884

Thanks for the assistance. The problem was that I had an ancient version of Pillow installed in ~/.local. I deleted it and everything works fine now.

Here's the output anyway:

>>> dir(Image)
['ADAPTIVE', 'AFFINE', 'ANTIALIAS', 'BICUBIC', 'BILINEAR', 'BOX', 'CONTAINER', 'CUBIC', 'DECODERS', 'DEFAULT_STRATEGY', 'DecompressionBombWarning', 'ENCODERS', 'EXTENSION', 'EXTENT', 'FASTOCTREE', 'FILTERED', 'FIXED', 'FLIP_LEFT_RIGHT', 'FLIP_TOP_BOTTOM', 'FLOYDSTEINBERG', 'HAMMING', 'HAS_CFFI', 'HUFFMAN_ONLY', 'ID', 'Image', 'ImageMode', 'ImagePointHandler', 'ImageTransformHandler', 'LANCZOS', 'LIBIMAGEQUANT', 'LINEAR', 'MAXCOVERAGE', 'MAX_IMAGE_PIXELS', 'MEDIANCUT', 'MESH', 'MIME', 'MODES', 'NEAREST', 'NONE', 'NORMAL', 'OPEN', 'ORDERED', 'PERSPECTIVE', 'PILLOW_VERSION', 'QUAD', 'RASTERIZE', 'RLE', 'ROTATE_180', 'ROTATE_270', 'ROTATE_90', 'SAVE', 'SAVE_ALL', 'SEQUENCE', 'TRANSPOSE', 'USE_CFFI_ACCESS', 'VERSION', 'WEB', '_E', '_ENDIAN', '_MAPMODES', '_MODEINFO', '_MODE_CONV', '__builtins__', '__doc__', '__file__', '__name__', '__package__', '_check_size', '_conv_type_shape', '_decompression_bomb_check', '_fromarray_typemap', '_getdecoder', '_getencoder', '_getscaleoffset', '_imaging_not_installed', '_initialized', '_plugins', '_show', '_showxv', '_wedge', 'alpha_composite', 'blend', 'builtins', 'cffi', 'coerce_e', 'collections', 'composite', 'core', 'deferred_error', 'effect_mandelbrot', 'effect_noise', 'eval', 'fromarray', 'frombuffer', 'frombytes', 'fromqimage', 'fromqpixmap', 'fromstring', 'getmodebandnames', 'getmodebands', 'getmodebase', 'getmodetype', 'i8', 'init', 'io', 'isImageType', 'isPath', 'isStringType', 'linear_gradient', 'logger', 'logging', 'math', 'merge', 'new', 'numbers', 'open', 'os', 'preinit', 'radial_gradient', 'register_decoder', 'register_encoder', 'register_extension', 'register_mime', 'register_open', 'register_save', 'register_save_all', 'registered_extensions', 'struct', 'sys', 'warnings']

>No more bandwidth to download files, so stopping for now

I'm sorry, what?

AUR guy here. Going on holiday and I don't have a copy of Arch to hand. I might be able to just update the git hash but I can't guarantee it will work (that said, recently nothing has gone wrong). Is that acceptable?