Posted: Tue Jan 23, 2018 11:27 am Post subject: Bug: Reset Tivo w/active transfer results w/pyTivo failure
If the Tivo transfer is interrupted from the Tivo side; the pyTivo is left in an indeterminate state; that is it will not stop/finish/end/terminate the current download. Worse - the user cannot 'terminate' current download. The only way to reset from this indeterminate state is to reset pyTivo.
Steps to reproduce: 1. Initiate a transfer using pyTivo.
2. Before transfer is complete; reset Tivo box
pyTivo will show that the file is being transferred
Checks to network activity will confirm that no transfer is occurring.
If file is monitored for an extended period of time; file will not complete transfer.
3. Find file being transferred in pyTivo in step 1 and attempt to terminate transfer (click on "Unqueue")
4. Re-initiate transfer of file (in step 1)
File will be in a permanent "Queued: 0" state.
System should automatically detect failure; log failure and terminate transfer. (optional: when user terminates transfer by clicking on "Unqueue"; the system should allow for transfer to that Tivo unit without resting pyTivo each time (with the loss of data).
User is forced to reset pyTivo. This has significant ramifications; most important being the loss of all data that was for completed transfers (for all Tivo boxes); requiring manual search to determine if files have been transferred.
There are sub-problems that exacerbate this; as noted there is no session-to-session retention of files that have already been successfully downloaded. Related: Files that have been downloaded have a (incrementing) number as a file name suffix; and if multiple files are set for download determine which files may have already been downloaded is painful (files need to be converted to '.mpg' before you can determine which was successful; that is where your download ended.) There is no persistent "Save metadata to .txt" option; so again if the user were to choose to not want this (feature request: Add it!) or of the user forgot to check "Save metadata to .txt" then the ability to determine when the failure occurred is hampered.
Current configuration: Three Tivo's connected (Series 2; Series 3 and Premiere). This type of failure has occurred with any / all of the systems.
Other forms of interruption will also induce this failure (Example: transfer from Tivo-Tivo when pyTivo is running for example).
I believe this is configuration agnostic; and as such no config file are included for the sake of brevity. If deemed necessary they will be added.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum