Is there an existing issue for this?
Current Behavior
Until 2025-06-06 each torrent was downloaded in the same folder. Since the update from 2025-06-07 it creates a sub folder for each torrent
Before :
\torrents_epub_\LazyLibrarian
------\name_of_torrent_1
------------\file_1_of_torrent_1
------------\file_2_of_torrent_1
------\name_of_torrent_2
------------\file_1_of_torrent_2
------------\file_2_of_torrent_2
After :
\torrents_epub_\LazyLibrarian
------\name_of_torrent_1
------------\name_of_torrent_1
------------------\file_1_of_torrent_1
------------------\file_2_of_torrent_1
------\name_of_torrent_2
------------\name_of_torrent_2
------------------\file_1_of_torrent_2
------------------\file_2_of_torrent_2
Any idea why it does this ? I didn't change anything except updating the docker image each time there's a new latest version.
Can't find the (new ?) setting that causes that
Expected Behavior
No duplication of folder
Steps To Reproduce
Every version after 2025-06-07
Last good version : c69fa2fd-ls158 (sha256:4a8571e2438eb45fc544ba40e54ae2bff30ac925a7c47bd06467f4812d434f6e)
Environment
- OS:DSM
- How docker service was installed:Portainer (docker compose)
CPU architecture
x86-64
Docker creation
Container logs
Is there an existing issue for this?
Current Behavior
Until 2025-06-06 each torrent was downloaded in the same folder. Since the update from 2025-06-07 it creates a sub folder for each torrent
Before :
\torrents_epub_\LazyLibrarian
------\name_of_torrent_1
------------\file_1_of_torrent_1
------------\file_2_of_torrent_1
------\name_of_torrent_2
------------\file_1_of_torrent_2
------------\file_2_of_torrent_2
After :
\torrents_epub_\LazyLibrarian
------\name_of_torrent_1
------------\name_of_torrent_1
------------------\file_1_of_torrent_1
------------------\file_2_of_torrent_1
------\name_of_torrent_2
------------\name_of_torrent_2
------------------\file_1_of_torrent_2
------------------\file_2_of_torrent_2
Any idea why it does this ? I didn't change anything except updating the docker image each time there's a new latest version.
Can't find the (new ?) setting that causes that
Expected Behavior
No duplication of folder
Steps To Reproduce
Every version after 2025-06-07
Last good version : c69fa2fd-ls158 (sha256:4a8571e2438eb45fc544ba40e54ae2bff30ac925a7c47bd06467f4812d434f6e)
Environment
CPU architecture
x86-64
Docker creation
Container logs