-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
typeerror in postprocessing #3341
Comments
What indexers are you using where lidarr finds better results? |
I dug into this a couple years ago, my recollection is fuzzy, but if I recall correctly there were two issues. First that lidarr supports picking categories for each indexer and second that it detects if the indexer supports album and artist as search parameters. I maybe misremembering this, but I'm certain that if I logged what comes back to headphones the match list was really poor, but the same album search in lidarr was all on point. In lidarr I've just got bitsearch, tpb, limetorrents, and solid torrents. Do you know why extract_data() would be not working when the file name is matching? I put the regex into a python regex tester and it matches on the name fine. I'm thinking there are a couple of byte vs string problems in this code maybe? |
I think extract_data() maybe has been broken for a while due to byte array and string mismatches. I don't have a setup to easily try a fix now that I'm using docker. I took a quick look at lidarr. It calls the provider with ?t=caps and gets a response like this below. q for music-search might also indicate the indexer supports sending album and artist for query. This one below doesn't. But I think the thing that makes a big difference is the category selection in lidarr. It prompts the user with the category list to select which to use. You can see this one below has a custom category 104627 for music. Headphones I believe is hardcoding the standard categories. Could we change the jackett indexer config to let the user override the hardcoded list of category numbers for each indexer? Or maybe just to add additional category numbers.
|
Do you mind testing the typeerror-fix branch? |
Unfortunately it was not enough. I tried to keep plugging errors but kept hitting more and more. postprocessor line 243 errors: Then in metadata.py this line errored Then I got this error and gave up :-)
|
@rembo10 steve
|
This is super awesome.... Thank you so much for doing that... Will get it merged in a few hours |
@dsm1212, made a change to the Torznab search to use the parent Using |
@rembo10 Tried the update to include the 3000 parent category. It's definitely better. I set up the same search engines in both lidarr and headphones. I tried a half dozen searches and I thought I found some differences but it was due to size limits. So is looking good so far. thanks! |
I'm having a new post processing problem though. Did one of these recent changes alter postprocessing to chmod the files before copying to the destination? It looks like the chmod is happening before the file copy now. This is a bad idea because the incoming files are owned by qbittorrent and the headphones user cannot chmod them. I'm sure it must have done the chmod after the copy previously because I was able to ingest files and now they all fail. I run both headphones and qbittorrent non-root maybe the change wasn't tested this way. |
I can't for the life of me figure out why I never had this post processing chmod issue. I looked at the code and it appears to have always done a chmod on the incoming files if file_permissions_enabled is true. I looked even in a three year old backup of my config.ini and it had a 1 value. Maybe that was evaluated to false because it was not true? My current file had True. The code which invokes this seems to be 6 years old. It's bizarre. But I set the setting to false and is working again. There is a bug in helpers.py though where it renames a file but then doesn't update the path variables that use the old file name. It comes up when processing an existing album. I'll create a separate bug and push a fix for it. |
I believe you merged my fix and this can be closed. |
Headphones seems to have stopped processing for me. I use lidarr to find/download because it uses site specific categories and is way better at finding things. But headphones has been super at postprocessing. Something changed and it stopped working. I get this trace below. It's barfing because the '-' probably needs to be b'-'. But I don't see why it got to this point. The helper extract_data() should have worked before this to parse the filename. But it apparently failed. Maybe due to another byte/string mismatch? The exception is not logged. Did something change recently that caused extract_data to be messed up with byte/string handling?
The text was updated successfully, but these errors were encountered: