Open uowiec opened 4 years ago
Where is this coming from? If it is a custom provider, the size needs to be available as bytes (int).
It's a private tracker, allow me not to mention the details. As I stated in the bug report, it is a custom provider, using RSS feed as data. This particular tracker uses 'GB' notation for file size. It does make sense to use the exact bytes number as the size, but is there any written rule for trackers to use int number of bytes in RSS feed? I have recently moved from SickChill and I never had this issue, but since Medusa displays this error all in red on the UI, I thought I better open an issue.
The only reason it "worked" is because the error is suppressed in SC. Which means the size is not used at all. We need this kind of info to be consistent and reliable, because we actually make use of it. It is really not great to ignore this kind of errors. The best thing would be to ask the provider to change it. Maybe we can add a fallback solution, will think about it.
INFO
Python Version:
3.6.9 (default, Nov 7 2019, 10:44:02) [GCC 8.3.0]
Operating System:Linux-4.15.4-041504-generic-x86_64-with-Ubuntu-18.04-bionic
Locale:UTF-8
Branch: master Database:44.14
Commit: pymedusa/Medusa@ee1b898d0f74750c4c265d077fcc0da73d17b41e Link to Log: https://gist.github.com/e813453b145cfcbe232cad631c1fc98eERROR
The search provider is RSS feed. Sample item:
STAFF NOTIFIED: @pymedusa/support @pymedusa/moderators