Lorenz Brun

@kelseyhightower Basically there would be a go template which is the same for every file. The data would be equal (structure-wise, not data-wise) but grouped up in directories, one for...

FYI I (the go-zfs author) am working on getting a ZFS exporter up and running. Once I have something we can work on integrating it into node_exporter.

I invite everyone here to give feedback on https://github.com/lorenz/zfs_exporter. As we get consensus on which metrics to expose, how and under what names we can start merging this back into...

Same with ``` ```

This is what my code already looks like, so this would be perfect.

@mark-i-m I agree that it is quite a bit of work, but there is no need for collaborating with kernel devs. The syscall interface is considered stable and they treat...

@mark-i-m What do you have in mind that you want changed? The syscall interface is totally usable from Rust and is in various ways a better fit than libc itself.

But this is not about implementing all possible safe uses of (for example) `mmap`, but just about reimplementing the standard library on top of syscalls which limits the scope to...

So I built EDS (3.44.2) and elementary Mail (7.0.0) with maximum debug symbols and no optimizations and ran the result through Valgrind (ASan didn't want to work, probably because I...

I can reliably reproduce it with a single message on a test account at least with optimizations turned off. It might very well behave in a probabilistic fashion if used...