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 ran into an issue where something seems to randomly choose from representing an integer field to be deserialized as either config's Value, or serde's Content. When it is the the first, the into_uint logic in Value correctly parses the string configuration (coming from an Environment source) but when it is running into deserializing Content::String then it fails with
Failed to parse config: invalid type: string "1234", expected u16
I could not figure out where the non-determinism is coming from.
I ran into an issue where something seems to randomly choose from representing an integer field to be deserialized as either
config
'sValue
, orserde
'sContent
. When it is the the first, theinto_uint
logic inValue
correctly parses the string configuration (coming from anEnvironment
source) but when it is running into deserializingContent::String
then it fails withI could not figure out where the non-determinism is coming from.
The following repository reproduces the problem:
https://github.com/vigoo/rust-config-bug
just running
cargo run
multiple times, sometimes it works, sometimes fails with the above error.The text was updated successfully, but these errors were encountered: