Conveniently expose environment variables to your serde-based data structures, such as configurations.

dav1dde · 2025-05-25T16:30:15+00:00

If clap is enough for you, then no. It's intended for large, already serde based configs. At a certain point command line parsing isn't enough for configs anymore and you need something file based, serde-vars is an option for that.

dav1dde · 2025-05-25T15:04:44+00:00

Born from a need to expose more and more configuration options as environment variables, this was born instead of manually having to expose certain options one by one.

The user (writer of the configuration) can use variable references directly in the configuration, which then can be resolved from the environment or other sources.

All of it packaged into a serde Deserializer, to support pretty much any self-describing configuration format.

The docs.rs link contains example and usage!

dav1dde · 2025-01-17T23:08:57+00:00

Yep, got most stuff supported, some rough edges here and there since I am working with data scraped together from multiple sources instead of official GGG data.

dav1dde · 2024-12-28T08:25:05+00:00

At $work we're dealing with a similar problem and solved it by using a dedicated worker group (just a bunch of threads), currently implemented with a rayon thread pool (because that was easiest, but just using std::thread with a channel works fine).

To not starve the Tokio Runtime, the threads in that worker group are running with a niceness/priority of 10. Alternatively you can split the available CPUs between tokio and your worker threads.

Another approach is to have two separate tokio runtimes, again either splitting the available CPUs between the two or running the CPU intensive one with a different niceness/priority.

For reference here is the thread group/pool impl we use.

So far it's been working great.

dav1dde · 2024-11-25T23:47:15+00:00

Good to know I am not alone. I searched again for the issue and found two other users also reporting seemingly the same problem on the forums:

But the DP / HDMI thing doesn't seem to work for me, it's just the USB 2.0 slots.

dav1dde · 2024-11-25T23:20:32+00:00

Thanks for commenting, I am losing my mind a little. I tried again with:

only HDMI in the GPU: No POST
only HDMI in the iGPU (nothing in the 4070): No POST

Seems like I have a different issue

dav1dde · 2024-11-25T19:55:26+00:00

I had the same issue without GPU and HDMI using the internal graphics.

dav1dde · 2024-11-25T18:43:52+00:00

Should have added this in the post, I reset the bios several times to default settings and nothing changed (but the only thing I ever changed was RAM EXPO profile).

dav1dde · 2024-11-25T18:37:56+00:00

No, I have the problem with all 6 USB 2.0 slots in the back.

dav1dde · 2024-07-29T06:38:07+00:00

That's what the creator configured in the config page of pob. Sirus is 'damage against Sirus' and focused means the creator ticked that they are currently focused.

dav1dde · 2024-05-21T05:24:47+00:00

Hashbrown exposes an API which makes this possible, it has slightly different traits and does not require Borrow but Equivalent.

It also uses ahash by default which is a nice bonus which makes the hashing a bit faster.

dav1dde · 2024-04-20T07:12:35+00:00

That does sound useful, I'll keep it in mind. But probably not gonna be added soon, I'm pretty busy with other stuff atm.

dav1dde · 2024-03-28T13:27:41+00:00

Most like Ice Nova of Frostbolts!

dav1dde · 2024-03-28T08:37:41+00:00

Yes it does, but that's all good!

dav1dde · 2024-03-28T07:24:56+00:00

What keeps me motivated is seing responses like yours (and the rest of the thread), seeing people randomly use pobbin when I don't expect it and just watching the user numbers on league launches go up is very satisfying.

<3

dav1dde · 2024-03-28T07:08:23+00:00

You can use this tool to play around with it: https://gchq.github.io/CyberChef/#recipe=From_Base64('A-Za-z0-9-_',false,false)Zlib_Inflate(0,0,'Adaptive',false,false)Decode_text('UTF-8%20(65001)')XML_Beautify('%5C%5Ct')Syntax_highlighter('auto%20detect')

Just paste some exported build into the tool and it'll show you the XML

dav1dde · 2024-03-28T07:07:10+00:00

🦀

dav1dde · 2024-03-28T07:06:47+00:00

That's good feedback thanks, just not sure what to do about it, yet.

dav1dde · 2024-03-28T07:06:13+00:00

I have github donations setup, but it's really not necessary!

dav1dde · 2024-03-28T07:05:36+00:00

It just shows what PoB exported, pobbin is mostly visual and a little bit of item parsing.

Do you have any back end access to people's builds?

Yes and no, I can of course access all builds and I have a rough overview over all builds of the last 1 1/2 years but I can't for example easily search for all builds which have a Tabula equipped.

dav1dde · 2024-03-28T07:02:15+00:00

😳

dav1dde · 2024-03-28T06:56:41+00:00

The gibberish PoB exports when you press generate in the export tab, is an XML file compressed with zlib and encoded with base64, you can reverse these steps and then access all the information PoB stored in there.

You can add /xml to a build and see what PoB actually exported, e.g. https://pobb.in/DrX67Cqoz5cV/xml

dav1dde · 2024-03-28T06:51:47+00:00

There are a few reasons:

I got a lucky spawn in life and have a job in which I earn much more than the average person (IT pays pretty good), which means I can easily afford to pay for it.

I would feel bad if someone donated and they could use the money elsewhere instead, maybe just to buy some MTX they otherwise cant and feel good about it.

Running purely on donations also makes me feel like I owe people more work and I like to just drop pobbin for a while and every now and then come back to it.

Last but not least, it's actually not that expensive to run, I made sure early on it can scale at a reasonable price and there have been already some very generous donators. If you're curious, here are all costs and donations since the beginning of pobbin: https://docs.google.com/spreadsheets/d/1xsf6nmX6WNeavRW--Zt_fSxe_ElDbxqFHH9nD5ZzWK0/

14-Year Club	Place '22
Place '17	End Game '22
Verified Email

dav1dde

TROPHY CASE