-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stream config toml file uses u64 #14
Comments
From looking at the implementation, it seems like this should be supported... |
OK, this is expected, ref. toml-rs/toml#512 We need a different on disk format which supports all data types. |
Yep, I guess we need to ditch the toml.
…On Tue, 14 Nov 2023 at 18:08, Tony Asleson ***@***.***> wrote:
OK, this is expected, ref. toml-rs/toml#512
<toml-rs/toml#512>
We need a different on disk format which supports all data types.
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABOSQZCGMRCZR2FGWXKVW3YEOXRPAVCNFSM6AAAAAA7JXAV5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJQHA2TCNBSGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Each stream in the archive has an associated
<stream id>.toml
that has the following fields:A simple example:
The problem is the
toml
code expresses numeric values as i64. If you try to read back a toml file that has values which exceed2**63-1
you'll get something like the following:Error { inner: ErrorInner { kind: NumberInvalid, line: Some(0), col: 10, at: Some(10), message: "", key: [] } }
This is when you're using toml version
"0.5.8"
.If you use the latest version of toml, you get the following error when you try to serialize:
Error { inner: OutOfRange(Some("u64")) }
The text was updated successfully, but these errors were encountered: