Negative timeout config value causes errors
|Assigned To:||Tomáš Strachota|
|Target version:||Foreman - Sprint 23|
|Found in release:||Pull request:|
|Velocity based estimate||-|
Our example config file advises to use -1 for infinite timeouts.
This can cause "time interval must be positive (ArgumentError)" exception on some ruby versions.
According to the docs the solution seems to be using 0 instead of -1.
We should change our sample config and check values < 0 before the timeout is set.
#1 Updated by Tomáš Strachota over 3 years ago
- Status changed from New to Ready For Testing
- Assigned To set to Tomáš Strachota
- Target version set to Sprint 22
#6 Updated by Tomáš Strachota over 3 years ago
- Status changed from Closed to Ready For Testing
Re-opening as I found some issues with different versions of rest-client: