-
Notifications
You must be signed in to change notification settings - Fork 4
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
index out of bounds
panic - Introduced from 0.5.0
release
#12
Comments
Hi @polarathene! Thanks for reporting the problem, I'll be working on it and will let you know as soon as I upload the new version |
@polarathene I've fixed the bug in the
It should raise an #[test]
fn test_gura_vec() {
let c = Config::builder()
.add_source(File::from_str(
r#"
hosts: [
"alpha",
"omega"
]
"#,
FileFormat::Gura,
))
.build()
.unwrap();
let v = c.get_array("hosts").unwrap();
let mut vi = v.into_iter();
assert_eq!(vi.next().unwrap().into_string().unwrap(), "alpha");
assert_eq!(vi.next().unwrap().into_string().unwrap(), "omega");
assert!(vi.next().is_none());
} Thanks! |
Wow that was really fast! I am not used to a bugfix so quickly, thank you! ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm trying to get Gura support merged into the
config-rs
crate, but seem to have run into a bug?The following test case is failing:
with the following error:
The bounds len will change based on the text for the
hosts
config, but is otherwise the same failure.It references the
0.5.1
crate I used withparser.rs
at line 1241, but I'm not sure what to make of that:gura-rs-parser/src/parser.rs
Line 1241 in 9cd3fa6
Backtrace
This failure appears to be due to a change in
gura-rs-parser
, but it's unclear what that could be as releases aren't tagged, nor is there any changelog.0.4.2
is working, and0.5.0
is where it appears to have broken.serde_gura
crate and re-using thejson5
serde logic we have, same failure while same generic code works for thejson5
format.crates.io does list each version published and the date. I can kinda leverage
git blame
withCargo.toml
to try track down version0.5.0
, crates.io states it was released Nov 25th 2021. Presumably this commit might be the one that introduced the bug? (or this one that followed after it, which was on the release day Nov 25th)The text was updated successfully, but these errors were encountered: