kia

joined 1 year ago
[–] [email protected] 40 points 2 weeks ago (3 children)
[–] [email protected] 22 points 3 weeks ago (8 children)

Now could you explain it like I'm 4?

[–] [email protected] 8 points 3 weeks ago
[–] [email protected] 6 points 3 weeks ago

The browser extension has a pin lock feature.

[–] [email protected] 1 points 3 weeks ago (6 children)

Well that failed quickly.

[–] [email protected] 37 points 1 month ago (1 children)

Going to be interesting when the neighbour's unstrapped house crashes into it.

[–] [email protected] 8 points 1 month ago* (last edited 1 month ago)

Will you have to refund him when Trump loses?

[–] [email protected] 8 points 1 month ago

PDFs are also editable...

[–] [email protected] 11 points 1 month ago

At this rate, he's going to put The Beaverton out of business...

[–] [email protected] 41 points 1 month ago

He has concepts of rallies.

[–] [email protected] 210 points 1 month ago (2 children)

Ask them for their bank login details so you can deposit the money directly into their account.

[–] [email protected] 12 points 1 month ago
 

In case you haven't seen it, here's a talk regarding Rust's integration into the Linux filesystem that gets completely derailed at The Linux Storage, Filesystem, Memory Management and BPF Summit.

 

I'm running into an issue accessing the Jellyfin web UI from Firefox (Chrome works fine). I try to log into an account but the spinner runs for a few seconds then disappears without logging in. When I reload the page, it appears I'm logged in, though all I see is the header and the rest of the page is blank. I get the following errors in console:

Uncaught Error: Permission denied to access property "ownerDocument"
Uncaught Error: Permission denied to access property "localName"

Has anyone else run into this issue?

 

Does anyone have any experience running Jellyfin on a Synology NAS that does not have container support? The Jellyfin installation guide recommends a Docker install for Synology. I have a Synology DS418 which apparently doesn't support Docker.

14
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
 

It seems like the key_value function has been removed from Cursor in 1.78.0-nightly. I've been using this to get the key/value pair from BTreeMap::upper_bound and BTreeMap::lower_bound.

Does anyone know why this was removed and what a good idiomatic alternative would be?

Edit: In case anyone encounters the same problem and is curious what's going on (the documentation hasn't been updated to reflect the change yet), it was referred to in this issue: 107540 changed in this commit: 8ee9693. Essentially, cursors in BTreeMaps previously pointed to specific nodes in the tree whereas now they point to gaps between the nodes. To get the node values, you need to use prev or next on the cursors returned by upper_bound or lower_bound.

 

The new instance icon looks great!

 

A while ago we had a post about a new instance icon. Just wondering if there's any news on that?

11
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

I'm getting errors such as "Socket: CLOSED" when I try to create comments, however the comment gets created. It then brings me back to the comment editing screen where if I click create again, it keeps duplicating the comment.

Wondering if anyone else is having this issue?

Edit: I get an error when creating posts as well: "stream was reset: CANCEL"

 

This is a really simple silly thing I just realized, but I noticed I have a lot code that looks something like this:

fn foo() -> Result<(), Error> {
    // do something
}

fn bar() -> Option<()> {
    let Ok(f) = foo() else {
        return None;
    };
}

I hated that if-statement. I realized today that I could simplify to:

fn bar() -> Option<()> {
    let f = foo().ok()?;
}

And that cleaned up my code a lot. It's a tiny thing, but when it's okay to discard the error from the result, makes such a big difference when you have a lot of them!

 

It released almost a ton of CO~2~.

view more: next ›