Aode (He/They)

asonix Now • 100%

I can only say "when it's ready." I think most of what I want to include in 0.4 is there, but I don't have a ton of time to work on it currently. I might see if I can get my last feature changes in this weekend, then it will be a matter of ensuring the 0.3 -> 0.4 upgrade is smooth, and that storage migration is solid

4

Lemmy Support Now

asonix Now • 100%

pict-rs doesn't keep track of how often it serves different images, so there's not a good metric for pruning old images. That said, 0.4 will introduce functionality for cleaning up processed images (e.g. resizes/thumbnails), removing their files & metadata. If they are viewed again, they will be re-generated.

0.4 will also include the ability to scale down images on upload, rather than storing the original resolution. This is not yet implemented, but it's on my roadmap.

All this said, it is already possible to use pict-rs with object storage (s3-compatible), rather than block storage. That's a good option if your hosting provider offers it

7

Rust Programming asonix • Now • 100%

pict-rs v0.3.0 and v0.3.1

git.asonix.dog

I've just published the stable version of pict-rs 0.3, and included a short write-up in the release description. Not much has changed since I posted about the betas, but check out the release anyway! - v0.3.0 changes: https://git.asonix.dog/asonix/pict-rs/releases/tag/v0.3.0 - v0.3.1 changes: https://git.asonix.dog/asonix/pict-rs/releases/tag/v0.3.1

11

2

Lemmy Support Now

asonix Now • 100%

what I noticed personally is that my pict-rs server had eaten 1,200MB of RAM, which is the limit I allowed that container. it was still working and it automatically restarted on crash so I didn't notice it oops

after I fixed the problem, my pict-rs server has been running at about 29MB for the last 12 hours. Significant improvement I'd say

3

Lemmy Support Now

asonix Now • 100%

for context: I am the pict-rs developer

8

Lemmy Support Now

asonix Now • 100%

Problem:

I gave tokio-console a buffer way too big

Fix:

Update pict-rs to at least v0.3.0-rc.7, which doesn't enable console by default

12

Lemmy Support Now

asonix Now • 100%

how long does it take for pict-rs to use up this memory?

2

Rust Programming asonix • Now • 100%

A Safe Async Runtime in Rust

git.asonix.dog

Hey all! Just wanted to share a little fun side project I've been working on recently. It's an ecosystem similar to smol for writing async rust code, but the internals make no use of `unsafe` at all ### repos: - `async-join`: a safe `join_all` function for `Vec<Future>` - `polldance`: a safe polling library built on unix `poll` with `rustix` for memory & io safety - `foxtrot`: a safe async reactor bulit on `polldance` and `rustix` - `jitterbug`: a safe async executor with multi-threaded work-stealing support I'm not here to say "you should definitely use this" because I've wirtten zero tests, and I've made no effort to implement standard apis like AsyncRead, AsyncWrite, etc, but I wanted to show it is possible to build these things yourself Shoutout to [rustix](https://github.com/bytecodealliance/rustix) for making socket programming safe and easy

8

0

Polls Now

asonix Now • 100%

Yes

3

Lemmy Support Now

What does this docker log error mean and can it be fixed?

asonix Now • 100%

If you don't know what OpenTelemetry is but you're having OpenTelemetry errors in your logs, it likely means that you have an opentelemetry_url set in your config when you shouldn't. You can get rid of the error by deleting that line, which will disable opentelemetry exports

3

Asklemmy Now

What web softwares lemmy`s team recommend to use to run an instance that respects privacy?

asonix Now • 100%

Lemmy and pict-rs support optionally exporting opentelemetry spans, and setting up Jaeger to capture those is a nice way to manage traces without shipping data to third parties

3

Unixporn Now

asonix Now • 100%

Plugin is likely lewis6991/gitsigns.nvim

4

Rust Programming Now

"Rust needs evert(), which turns an iterator over Result of T into a Result of a collection of T or a collection of errors" Thoughts on this?

asonix Now • 100%

playground link: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=39a1c5c855a4c3d5d537f446c3b72783

2

Rust Programming Now

"Rust needs evert(), which turns an iterator over Result of T into a Result of a collection of T or a collection of errors" Thoughts on this?

asonix Now • 100%

i might try

let res = collection.into_iter().map(|item| item.fallible_operation()).fold(Ok(Vec::new()), |acc, res| {
    match (acc, res) {
        (Ok(mut vec), Ok(item)) => {
            vec.push(item);
            Ok(vec)
        }
        (Err(mut vec), Err(error)) => {
            vec.push(error);
            Err(vec)
        }
        (Ok(_), Err(error)) => Err(vec![error]),
        (acc, _) => acc,
    }
});

Maybe expand it with

pub trait Evert<T, E> {
    fn evert(self) -> Result<Vec<T>, Vec<E>>;
}

impl<I, T, E> Evert<T, E> for I
where
    I: IntoIterator<Item = Result<T, E>>,
{
    fn evert(self) -> Result<Vec<T>, Vec<E>> {
        self.into_iter().fold(/* implementation from above */)
    }
}

fn main() {
    let result = vec![Ok(1), Err(3), Ok(4), Err(8)].evert();
    assert_eq!(result, Err(vec![3, 8]));
}

2

Polls Now

asonix Now • 100%

elementary OS

3

World News Now

asonix Now • 85%

With these examples I think the correlation is a little loose. Dr Lutchmedial died two weeks after his third shot. Claiming the vaccine was a direct cause when the only available evidence is a two week timespan is weak.

The other example provided doesn't demonstrate harm caused by a vaccine. It sucks that a deadly virus is deadly, and it sucks that the vaccine didn't help in this case. It's not a good argument against getting a vaccine.

5

Asklemmy Now