/hydrus/ - Hydrus Network

>>11863

Thanks Dev

>>11865

Thanks, the new list here is too tall. I will reduce its min height for 344.

>>11867

Test I now have a hydrus tablet, hoping I can keep up with messages better like this.

>>11863

Get an error using API /get_files/file_metadata

The repository encountered an error it could not handle! Here is a dump of what happened, which will also be written to your client.log file. If it persists, please forward it to hydrus.admin@gmail.com:

Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/home/kyck/.local/lib/python3.6/site-packages/twisted/_threads/_threadworker.py", line 46, in work
    task()
  File "/home/kyck/.local/lib/python3.6/site-packages/twisted/_threads/_team.py", line 190, in doWork
    task()
--- <exception caught here> ---
  File "/home/kyck/.local/lib/python3.6/site-packages/twisted/python/threadpool.py", line 250, in inContext
    result = inContext.theWork()
  File "/home/kyck/.local/lib/python3.6/site-packages/twisted/python/threadpool.py", line 266, in <lambda>
    inContext.theWork = lambda: context.call(ctx, func, *args, **kw)
  File "/home/kyck/.local/lib/python3.6/site-packages/twisted/python/context.py", line 122, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/home/kyck/.local/lib/python3.6/site-packages/twisted/python/context.py", line 85, in callWithContext
    return func(*args,**kw)
  File "/home/kyck/hydrus/include/ClientLocalServerResources.py", line 1243, in _threadDoGETJob
    media_results = HG.client_controller.Read( 'media_results_from_ids', file_ids )
  File "/home/kyck/hydrus/include/HydrusController.py", line 605, in Read
    return self._Read( action, *args, **kwargs )
  File "/home/kyck/hydrus/include/HydrusController.py", line 192, in _Read
    result = self.db.Read( action, *args, **kwargs )
  File "/home/kyck/hydrus/include/HydrusDB.py", line 955, in Read
    return job.GetResult()
  File "/home/kyck/hydrus/include/HydrusData.py", line 1519, in GetResult
    raise e
include.HydrusExceptions.DBException: TypeError: 'int' object is not iterable
Database Traceback (most recent call last):
  File "/home/kyck/hydrus/include/HydrusDB.py", line 581, in _ProcessJob
    result = self._Read( action, *args, **kwargs )
  File "/home/kyck/hydrus/include/ClientDB.py", line 9259, in _Read
    elif action == 'media_results_from_ids': result = self._GetMediaResults( *args, **kwargs )
  File "/home/kyck/hydrus/include/ClientDB.py", line 6053, in _GetMediaResults
    ( cached_media_results, missing_hash_ids ) = self._weakref_media_result_cache.GetMediaResultsAndMissing( hash_ids )
  File "/home/kyck/hydrus/include/ClientCaches.py", line 1913, in GetMediaResultsAndMissing
    for hash_id in hash_ids:
TypeError: 'int' object is not iterable

>>11873

Thank you for this report. I will fix this for next week. This has revealed a flaw in my testing regime that I will make a longer term job to fix as well.

>>11863

I can't access the repo. If I do what is asking, same error but with a dialog window instead of a toast.

2019/03/14 22:03:16: Exception:

2019/03/14 22:03:16: CancelledException

Upload cancelled: This hydrus service (hydrus service: official) recently failed to log in. Please hit its 'refresh account' under 'review services' and try again.

Traceback (most recent call last):

File "include\HydrusThreading.py", line 342, in run

callable( *args, **kwargs )

File "include\ClientGUI.py", line 4134, in _THREADUploadPending

service.Request( HC.POST, 'update', { 'client_to_server_update' : client_to_server_update } )

File "include\ClientServices.py", line 879, in Request

network_job.WaitUntilDone()

File "include\ClientNetworkingJobs.py", line 1155, in WaitUntilDone

raise HydrusExceptions.CancelledException( message )

include.HydrusExceptions.CancelledException: Upload cancelled: This hydrus service (hydrus service: official) recently failed to log in. Please hit its 'refresh account' under 'review services' and try again.

>>11876

Thank you for this report. If you check the service's review services page, what status does it report there? Normally, right under its address it says 'service is functional' and under the account section it says 'account is functional'. Do you have a specific error there with more info?

This error is something I have been trying to pin down a while. It seems to fix itself after a few days, maybe when some maxed bandwidth rules clear out. Does that panel have any odd bandwidth stuff going on?

>>11879

Ok, thank you. I will keep working on this. If you unpause the service on that panel, does the 'Repository is paused!' change to an error, or does it think it is fine?

>>11909

I think I did it with the same error when I first tried, however now it allowed me to unpause and refresh account worked. I guess as you said "It seems to fix itself after a few days" XD

>>11929

How does this work? Do you leave Hydrus running in the background and so long as the computer is awake you can access it via mobile? I don't understand.

t. brainlet

>>11928

Thank you. If you open a terminal and type 'which ffmpeg', where does it think it is?

The important value in your env there is the 'PATH'. It looks like /usr/bin and /usr/local/bin are in there, which are the usual missing suspects here. Is your ffmpeg somewhere else?

Also, if you go to install_dir/db/client - 2019-3.log and search for 'TERM_PROGRAM' to get to where this section was written to log, it looks like there should be a little bit more than what fit in the popup window. I do not think it is important, but is there LD_LIBRARY_PATH or LD_LIBRARY_PATH_ORIG in there, and if so, what is the value (the text after the the name and colon)? Please do check and scrub out anything personal again, although I think these values should be innocuous.

If your ffmpeg got installed to an unusual location not in the PATH there, then if you make a softlink to it like so:

ln -s /path/to/ffmpeg/ffmpeg /usr/local/bin/ffmpeg

Does it then work?

>>11929

Hey, this looks fantastic!

Yeah, I only have basic tag support in atm. Wildcard searches are actually dealt with in hydrus with a different search object, so what is being searched for there is literally the asterisk character rather than 'anything'. Namespace searches are the same–they use different code to run faster. It is unusual that 'namespace:' would work as a fixed tag but the same negation wouldn't, but this is an edge case anyway that isn't expected to ever run. I expect to add namespace and wildcard searches to the Client API in my future weekly work.

I will be adding more system search predicates as well.

Supporting tag autocomplete search sounds good as another extension. Perhaps until then you could have a 'favourites' list or similar to make quick-entry easier?

Unfortunately, hydrus does not support paginated searches like a booru would. It returns everything in one go, without sorting. If you have a technical limit to the number of thumbs you can display, I recommend you break the results list into chunks of your own preferred page size. Sorting results is unfortunately not (yet) possible at the db level, so you will have to do it yourself using data from the file_metadata calls.

Please keep me updated on how you get on here.

>>11932

I can't speak confidently for exactly how his system works, but yeah, you would have to have the client on for this to work, and maybe set up NAT port forwarding or use hydrus's in-built UPnP port forwarding, and then point your account settings in his phone app at either your fixed IP address and port or get yourself a no-ip.org kind of deal, like I do for the PTR.

>>11935

Thanks for the answers. Pagination is not a huge deal because thankfully most endpoints simply return ids or file hashes which I can then use to query files in chunks myself.

And yeah like you said, I could passively store tag information as I fetch files and keep a list. That should work ok until we get a tag search endpoint.

>>11932

As long as the hydrus app is running and has the client api enabled then yes, you can access it via the mobile app. You just need to set up access via review services > client api > add > from api request. You do that and enter your computers IP address and the port the api is using into the app and you're good to go.

This won't work outside your LAN though. You might need to take some extra steps to allow public access to your server. Steps like port forwarding, setting a static ip (for convenience's sake so you don't have to update your ip whenever it changes) and maybe even a domain name if you want to be extra fancy.

This isn't unique to hydrus or my mobile app though, these are the kinds of steps you would need to take to open up any kind of server to the world wide web that you're running on your home computer. If you're running a web server or ftp server or something it's the same deal.

>>11936

Out of curiosity, what platforms are you ultimately planning to release it for?

>>11933

I did which ffmpeg and got nothing so I brew installed it and now everything works great. No idea why I didn't have it. Thanks alot for the help

>>11937

I am developing using flutter which is cross platform. That means it will be available for iOS and Android. Submitting to iOS app store can be a headache though so I wouldn't be surprised if Android would be released first. However my intention is to release it for both

>>11939

If you plan to make it FOSS please submit it to the F-Droid.

>>11936

I see. So I can shitpost my memes from mobile yet leave my collection in Hydrus and not waste my limited phone space. I can use this.

>>11940

Yes please this. I'd rather F-droid than google play anyway, which I use for Clover as is.

>>11940

>>11942

I hadn't heard of F-Droid before. I'm not familiar with what needs to be done to release there. I'll definitely look into it and try my best to get it submitted. Hopefully it's as simple as submitting the same apk you'd submit to the play store.

>>11929

>>11932

>>11937

>>11940

>>11942

I should say at this point that the Client API is still prototype, so atm it is http only, which means comms are unencrypted. This is fine when on the same machine or your LAN, but for remote connections, this is not great. Before we jump on doing a phone app for real-world use, I will have to add https (albeit with self-signed certificates, since we are talking IP addresses and not paid-for domains).

>>11938

Great, I am glad we sorted it out!

>>11938

>>11950

I should say, I'll improve the error reporting here.

>>11947

Eh, it'll get there eventually. I still haven't imported most things since I want to preserve original creation date. Although I guess the chan filenames being unix time means they could be converted later

>>11947

Yeah, encryption would be pretty important. I personally don't care because lol openvpn server at home, but that's not normal.

>>11955

The numbers there are the 'status' of that list of tags. In hydrus, a file's tags can have four different statuses:

0 - current - the file has the tag for this service

1 - pending - this tag is pending to the service

2 - deleted - this tag was current but has now been deleted

3 - petitioned - this tag is current and is petitioned for deletion

Pending/petitioned relates to the 'pending' menu in the main hydrus client gui. Repository tags are not fixed as current/deleted until pending/petitioned are commited through that menu.

In writing this out, I realise I fucked up here because a 'local tags' service won't ever have 'pending' tags. I will rewrite this help section to have it refer to a hypothetical tag repository.

>>11964

To follow up here, if you wish to edit a file's tags with /add_tags/add_tags, you will need to use this more detailed tag status information to figure out if you are 'petitioning' or 'rescind pending' or whatever.

For practical purposes, if you want to calculate what tags the file currently 'has' for easy phone display, you can go:

tags = ( current ∪ pending ) - petitioned

Petitioned tags are pretty rare, so you can probably just go ( current ∪ pending ). You'll then be unioning those sets across all given service_names to get a file's 'all known tags' as you would see in the client.

>>11964

>>11965

Ah. I forgot tags can have statuses. Thanks for clarifying