You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
If you have any non-completed torrents, container restart will result in empty "added" field.
I am not sure where exactly problem lies and I have never used rutorrent/rtorrent standalone and so I have no idea where even to begin. Because I am using the docker image, I decided to start issue here, seeing as how stickz is also very active here.
Screenshots before and after restart
Expected behaviour
Added date stays the same.
Actual behaviour
Added date is gone.
Steps to reproduce
Add a torrent such as Ubuntu ISO.
Verify it is showing up in a web UI.
Do docker compose down && docker compose up -d.
Refresh web UI.
Notice that "Added" field is empty for the added torrent.
This may have to do with time between RT_SESSION_SAVE_SECONDS? I put in a request (I can't remember where or find it, maybe I was dreaming) to be able to manually force a session save (or do any of you have any idea how?). Basically my thinking is that if you restart having added torrents after the last session save...that of course it will start back up with the last saved session info?
Support guidelines
I've found a bug and checked that ...
Description
If you have any non-completed torrents, container restart will result in empty "added" field.
I am not sure where exactly problem lies and I have never used rutorrent/rtorrent standalone and so I have no idea where even to begin. Because I am using the docker image, I decided to start issue here, seeing as how stickz is also very active here.
Screenshots before and after restart
Expected behaviour
Added date stays the same.
Actual behaviour
Added date is gone.
Steps to reproduce
docker compose down && docker compose up -d
.Docker info
Docker Compose config
No response
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: