I wouldn’t mind having a explanation of what you want to do instead of the code. It’s not quite clear what you mean.

Anyways, what you want is to transform an iterator (your Select) into an iterator of Option<String>?

For that, there’s multiple ways but here’s the simplest:

link_nodes.map(|node| node.value().attr("href").to_string())

Essentially, for each elements, we execute a closure (arrow function in JavaScript) that transform the node into your href string.

P.S. can’t guarantee it works, I don’t know what this “Select” type is, and I’m programming on mobile

No idea for Tiberius, but for SQLite I’m stuck with converting to timestamp and back. Ugly but works

P.S. add a getter to your data struct and you can be “seamless”

Sadly sqlx seems to have gone semi-proprietary with their MSQL driver. Personally never understood the appeal of mssql when there’s Postgres and SQLite, but hey, it does work.

I’ve started using welds as my new ORM of choice as SeaORM and Diesel is just not a friendly experience, and supports Mssql OOB. So it’s nice there’s still options for it.

Half joking. Lifetimes can be hard but once you understand the concept it’s quite easy.

The second joke is about you never learn Rust. You’re always on the learning rollercoaster. Always one step away but each time it makes you rethink the whole language.

Don’t get me wrong, I’m a rust main. But does issues does exist

Rewrite it in rust. Now get a lifetime of problems

Oh no. This is so bad. Who in their right mind would assume that a login user remains the same user throughout the session!?

Oh wait. Windows.

What? No! I leave at 6pm. (But start at 2)

What

I get 100m up front, right?

Right?

? I’m agreeing with you?

There’s a difference between helping people with misunderstanding a tool and belittling them for being wrong. It’s just a matter of wording that separate an helpful answer from a toxic one

I could tell you “You should actually use Y instead of X. They are numerous benefits like A, B and C. The doc actually have a great example you may have missed or not understood it was for this purpose. It will help you a lot more than what you are thinking of doing.” And this would be fine.

But “Just use Y. X is bad because Y is made for that. You not willing to use Y shouldn’t make you do X. There’s even a the first Google link on how to do it” isn’t fine.

And I have not belittled them at all. I have said that it wasn’t what I was looking for. A lot of times people post questions they think should solve their issue, but only to realise that they didn’t fully understand the full picture and theirs problem is on a larger scale.

Seems like the best solution. I’ll look into it

But can it prevent killing only docker, and not the build/big containers processes?

Oh that’s not a problem to let a container get killed. It’s perfectly fine. What I want is just not crippling my whole server because one container did a funny.

If it keeps docker and the portainer VM I’ll be 100% ok, because I can just restart it. I don’t want to have remote access to my server outside of my home for security reasons, so this is just the bare minimum

Alright, sorry for calling it a “bandaid fix”. It wasn’t just the right term for what I wanted to say. I was more referring on how it would only fix issues in cases of builds, and not on actual runtime, which can also be an issue if I am not careful. So yeah, it’s the fix for the issue in the post, but this solution made me realise that this isn’t the only thing I want.

But the second part is… Just chill. It’s a home server. Not a high availability cluster. I can afford stupid things. Heck, I’m only asking this question because I got stupid and haven’t limited the job count of a cargo build, downing my server. I don’t care that my build crash. I just want to not have to manually restart it, because when I’m not here I can’t do it.

As for the link that you sent, it’s container limitations, not image building limitations. And I already have setup some on my most hungry container, stats shown that it blew past it, so idk what’s going on there.

Edit: NVM. This is a bandaid fix. What if you forgot to put the flag? Like it’s been 5 month since last time and forgot to do the same fix? Or you accidentally removed it while editing the command? I’m actually looking for a solution that fixed my problem fully, not a partial solution

Fair enough. But I don’t want a bandaid fix solution. Even more that I do all my docker through portainer and the option isn’t there.

It could also be useful if a container got a memory leak and is unbounded

I’ll try that. I know that systemctl has a start-or-reload command, but is there any “start-or-ignore” commands? Or start flags?

You’re lost. This ain’t the place to post that.

Also “candy box” is a waffle menu

Probably a joke

I would do that… If CI wouldn’t be set to -D warnings

Who even does that? Oh wait, it was me.

Joke aside, it does help to keep the code clean, even more for open source projects where multiple separate people may all have their own codding style, and it helps make it easier to organise.

But I do agree that it can be really, really annoying.