-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
NFO file not created #609
Comments
LOGS:
So I can see 2 separate problems here (I think)
If the problem is caused by folder permissions on my host, could someone advice how to set them properly. But since the the other files getting created, I really cant see that beeing the problem |
Ok, so I managed to add some logging myself Since I don't know Python, I'm not going to try fix this myself.
First row from download_media, where the filename is a path within the container
|
This looks like a path or volume issue. What's |
Yes, but in write_text_file the TubeSynk part gets replaces by the symlink for TubeSync on my host I'm happy to add more logs if it would help. Relevant parts of my docker compose file
Relevant Symlinks on my server |
Do you have some custom container config? What does your setup use |
No, I don't think I have something custom, except for using symlinks containing another symlink on my host I added som more logging, but it doesn't really add anything relevant. Did a new run for a different file
|
I removed the call to file_is_editable on my local setup
Now a NFO is created alongside the other files again. While this isn't a real sollution, it works for me until a real sollution can be found. |
Since about a week, NFO files are no longer created for my downloaded videos.
I have this option ticked for all my channels.
I can see the info embedded in the mkv-file, so there is not a problem with getting the description
For the videos I also save an image for, the image is still created.
EDIT
I also tried ticking the export json file, which works. So it seems to be only the export NFO that has been broken
The text was updated successfully, but these errors were encountered: