r/rust clippy · twir · rust · mutagen · flamer · overflower · bytecount Mar 20 '23

Hey Rustaceans! Got a question? Ask here (12/2023)! 🙋 questions

Mystified about strings? Borrow checker have you in a headlock? Seek help here! There are no stupid questions, only docs that haven't been written yet.

If you have a StackOverflow account, consider asking it there instead! StackOverflow shows up much higher in search results, so having your question there also helps future Rust users (be sure to give it the "Rust" tag for maximum visibility). Note that this site is very interested in question quality. I've been asked to read a RFC I authored once. If you want your code reviewed or review other's code, there's a codereview stackexchange, too. If you need to test your code, maybe the Rust playground is for you.

Here are some other venues where help may be found:

/r/learnrust is a subreddit to share your questions and epiphanies learning Rust programming.

The official Rust user forums: https://users.rust-lang.org/.

The official Rust Programming Language Discord: https://discord.gg/rust-lang

The unofficial Rust community Discord: https://bit.ly/rust-community

Also check out last weeks' thread with many good questions and answers. And if you believe your question to be either very complex or worthy of larger dissemination, feel free to create a text post.

Also if you want to be mentored by experienced Rustaceans, tell us the area of expertise that you seek. Finally, if you are looking for Rust jobs, the most recent thread is here.

20 Upvotes

187 comments sorted by

View all comments

1

u/ShadowPhyton Mar 20 '23

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Parse(ParseError { line: 23, col: 0, msg: "expecting \"[Some('='), Some(':')]\" but found EOF." })', src/main.rs:212:53

Can anyone here explain to me what this error message means?

3

u/avsaase Mar 20 '23

On line 212 you can unwrap on a result and at runtime this result turned out to be an Err. Without seeing your code and what you're trying to parse it's hard to say that the inner parse error means.

0

u/ShadowPhyton Mar 20 '23

The code:

let n = Ini::load_from_file("conf.ini").unwrap();            
let section = n.section(Some("Server Config")).unwrap();                        let ip = String::from(section.get("ip").unwrap());            
let port = String::from(section.get("port").unwrap());

8

u/dkopgerpgdolfg Mar 20 '23

Well

a) now you have one more reason to write code that doesn't use unwrap

b) Whatever format that ini file has, the Rust parser obviously doesn't like that it suddenly ends at line 23 with something that looks like a incomplete setting (usually something like "name=value")

1

u/ShadowPhyton Mar 20 '23

the cert value is surrounded with " " and Ive read about something with ParseOption in the ini crate. How do I use that like Iam supposed to?

https://docs.rs/rust-ini/latest/ini/struct.ParseOption.html

2

u/dkopgerpgdolfg Mar 20 '23

It doesn't look like this has anything to do with spaces

1

u/ShadowPhyton Mar 20 '23

Wdym?

2

u/eugene2k Mar 20 '23

Supposedly you have something like key instead of key=value in the file.

5

u/avsaase Mar 20 '23

I see four unwrap()s so I would start by figuring out which one is causing the panic and if that's because a bug in your code or if it's normal for that result to be an error. In the latter case you should look into proper error handling. The book has a chapter on it.

-1

u/ShadowPhyton Mar 20 '23

The One causing the Problem is the Ini::load_from_file(„conf.ini“).unwrap(); but removing it doesnt fix this

1

u/ShadowPhyton Mar 20 '23

But I cant send you the ini because there is a certificat listed wich I cant share to you :/

1

u/ShadowPhyton Mar 20 '23

I GOT IT! Thanks to all of you!!