Torrents are being shown as short of the 336 hour requirement. The application is using added on metric instead of time active(seeded time) This results not being able to get close to the 336 hour requirement but rather having to wait longer just so items are in violation of seeding policy.
Torrents are being shown as short of the 336 hour requirement. The application is using added on metric instead of time active(seeded time) This results not being able to get close to the 336 hour requirement but rather having to wait longer just so items are in violation of seeding policy.
Review data output and determine format of Transfer Time active
Change qclient.py to use the time active metric for protected torrents but still use added on for non protected torrents
Write test cases
- [ ] Review data output and determine format of Transfer Time active
- [ ] Change qclient.py to use the time active metric for protected torrents but still use added on for non protected torrents
- [ ] Write test cases
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Torrents are being shown as short of the 336 hour requirement. The application is using added on metric instead of time active(seeded time) This results not being able to get close to the 336 hour requirement but rather having to wait longer just so items are in violation of seeding policy.
Review data output and determine format of Transfer Time active
Change qclient.py to use the time active metric for protected torrents but still use added on for non protected torrents
Write test cases