Skip to content
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

invalid type: floating point #7

Closed
D1mon opened this issue Jan 30, 2020 · 4 comments · Fixed by #8
Closed

invalid type: floating point #7

D1mon opened this issue Jan 30, 2020 · 4 comments · Fixed by #8

Comments

@D1mon
Copy link

D1mon commented Jan 30, 2020

error: invalid type: floating point 264.50300000033167, expected i64 at line 1 column 1

har file:

"time":` 264.50300000033167,

error: Error(
    Yaml(
        Message(
            "invalid type: floating point `264.50300000033167`, expected i64",
            Some(
                Pos {
                    marker: Marker {
                        index: 0,
                        line: 1,
                        col: 0,
                    },
                    path: ".",
                },
            ),
        ),
    ),
    State {
        next_error: None,
        backtrace: InternalBacktrace {
            backtrace: None,
        },
    },
)
@mandrean
Copy link
Owner

mandrean commented Feb 5, 2020

Hi @D1mon! I'll try to reproduce your error and see what I find!

Meanwhile: Is that before264...` a typo or actually a part of your HAR file?

@D1mon
Copy link
Author

D1mon commented Feb 5, 2020

in the ".har" file there are many such values (floating point). I can send the file to mail. I took the har request from chromium and saved it.

@D1mon
Copy link
Author

D1mon commented Feb 5, 2020

I deleted the floating part in the whole file and it worked.
264.50300000033167 -> 264

@jackinloadup
Copy link
Contributor

This seems to be more of an issue with Chrome HAR files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants