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
I have read the pinned issues and could not find my issue
Is there an existing or similar issue/discussion for this?
I have searched the existing issues
I have searched the existing discussions
Is there any comment in the documentation for this?
I have read the documentation, especially the FAQ and Troubleshooting parts
Is this related to a provider?
I have checked the provider repo for issues
My issue is NOT related to a provider
Are you using the latest release?
I am using the latest release
Have you tried using the dev branch latest?
I have tried using dev branch
Docker run config used
I'm using a docker-compose.yml. This compose file has worked for years and suddenly it stopped, even though I did not change anything.
The relevant part is this environment variable.
TRANSMISSION_RATIO_LIMIT
I had set it to 2.0. Always worked. Suddenly, it started getting a ValueError, because this Float was parsed as an Int.
Transmission always silently failed. You could only see that it failed, when you exec into the container and run something like ps auxf, to see OpenVPN, but not Transmission running.
The initial error, indicating that something was wrong in the first place, was connection refused when trying to connect to 9091.
Current Behavior
ValueError on Float, without warning.
Transmission not running is never indicated or noticed by the deployment.
Expected Behavior
When Transmission crashes for whatever reason, it should crash the entire container or at least show a big fat ERROR in the logs, repeatedly.
Whether parsing the number as Float, rather than Int, makes more sense, is debatable.
How have you tried to solve the problem?
Changed Float to Int.
Log output
Could not coerce TRANSMISSION_RATIO_LIMIT value 2.0 to expected type <class 'int'>
Traceback (most recent call last):
File "/etc/transmission/updateSettings.py", line 74, in <module>
env_value = setting_type(env_value)
ValueError: invalid literal for int() with base 10: '2.0'
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Docker run config used
I'm using a
docker-compose.yml
. This compose file has worked for years and suddenly it stopped, even though I did not change anything.The relevant part is this environment variable.
I had set it to
2.0
. Always worked. Suddenly, it started getting aValueError
, because this Float was parsed as an Int.Transmission always silently failed. You could only see that it failed, when you
exec
into the container and run something likeps auxf
, to see OpenVPN, but not Transmission running.The initial error, indicating that something was wrong in the first place, was
connection refused
when trying to connect to9091
.Current Behavior
ValueError
on Float, without warning.Transmission not running is never indicated or noticed by the deployment.
Expected Behavior
When Transmission crashes for whatever reason, it should crash the entire container or at least show a big fat ERROR in the logs, repeatedly.
Whether parsing the number as Float, rather than Int, makes more sense, is debatable.
How have you tried to solve the problem?
Changed Float to Int.
Log output
HW/SW Environment
Anything else?
When Transmission is not working, OpenVPN running, as if nothing were wrong, is misleading.
The text was updated successfully, but these errors were encountered: