fix(agent): Handle float time with fractions of seconds correctly #12491
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the course of #12490 I found an issue when specifying a duration with fractions of seconds as a plain floating point value e.g.
timeout = 1.5
, where you would expect the timeout to be 1500 milliseconds. However the current code will just floor that value to 1 second.This PR fixes the handling of plain floating point values that contain fractions of seconds and also gets rid of the necessity for TOML quotation handling by using the
UnmarshalText
interface.