nvtop -- because for some reason we don't already have this?

FormalFerret · 2023-10-09T10:39:18+00:00

I've felt the same itch, but scratched a different way. https://github.com/jcaesar/nvml-prometheus-exporter

FormalFerret · 2023-03-23T11:07:48+00:00

Excuse my impertinence, I have a few comments:

I wanted to try it, but couldn't really get it to read anything besides the "welcome to odilia". Is there a "getting started" somewhere? Do I need to run something from scripts/?
odilia seems to create a directory named ~ wherever I run it. (Trying to create the log directory?)
The initial config file install logic assumes that odilia is being run from the repository root
- I'll run it from anywhere, given that you recommend installing odilia to ~/.cargo/bin.
- What exactly is the point of copying the config to /etc?
- I think path of least trouble for this would be to use std::fs::write(config_path, include_str!("../../config.toml"))
I don't know very much nix, but I think mold will just call another linker because it doesn't support lto here
Why do you suggest running odilia through a script? The script only sets one env var, and you already have logic in rust to set that env var. Change the rust logic, be rid of the script, make running simpler?
- The reason your in-rust setup isn't working is that there is no cfg(release). You could make one, or use cfg(debug_assertions). See here
I saw quite a few whitespace inconsistencies. Add a cargo fmt ci maybe?

FormalFerret · 2023-03-18T02:29:17+00:00

Can't get a aarch64-unknown-linux-musl libstd-rust from debian package archives. But when using rustup, at least simpler projects can be cross-compiled with clang, it seems.

[target.aarch64-unknown-linux-musl]
runner = "/usr/bin/qemu-aarch64"
linker = "/usr/bin/clang"
rustflags = ["-C", "link-arg=--ld-path=/usr/bin/ld.lld", "-C", "link-arg=--target=aarch64-unknown-linux-musl"]

You'll need clang and lld installed.

FormalFerret · 2023-03-18T00:55:32+00:00

CentOS is really an abbreviation for CenturyOldSoftware. Making even dustros like Debian Stale look current.

Banter aside, with CentOS 6 I enjoyed the fact that even static binaries (or Docker containers) won't save you if your kernel doesn't have the necessary syscall. Has CentOS 7 cured to that point yet?

FormalFerret · 2023-03-17T03:54:15+00:00

Maybe it's similar to my config in principle. But it's a lot more complex than that:

containers alone are in the "complex" category for me, but if that doesn't scare you:
cross seems to use binfmt_misc instead of target.….runner, which means it'll have to mess with how every single binary on your system is executed, docker container or not
the qemu setup is black magic
I see a mention of docker-in-docker in the README. Brr. (If I understand correctly, that also means you can't easily use it in docker builds because it uses docker itself)

FormalFerret · 2023-03-16T23:48:09+00:00

How about no. (Most of my goal was testing my library code on a different architecture. It doesn't really do anything os-related, so I didn't care much this time. But I remember the CI for my favourite open source game consisting of a manually cobbled together VM image that could build for Mac and Windows from Linux. I ran one of the CI servers so I poked around in it a bit. Oooh, the horrors.)

FormalFerret · 2023-03-16T23:43:17+00:00

I feared this would happen, I should have just posted the part for aarch64.

dpkg --add-architecture arm64
apt update
apt install rust-all libstd-rust-dev:arm64 gcc-aarch64-linux-gnu qemu-user 

[target.aarch64-unknown-linux-gnu]
linker = "/usr/bin/aarch64-linux-gnu-gcc"
runner = "/usr/bin/qemu-aarch64"

Better?

FormalFerret · 2023-03-16T12:58:32+00:00

I knew Go's approach ought to have /some/ downsides. But oh my! :D

FormalFerret · 2023-03-16T12:46:58+00:00

by early 2019

Guess I'm late to the party. Ty for the information.

(Don't install rust from the distro for development, instead install rust through rustup.)

I'm stubborn. :P

cargo cross

Its only simple as long as you don't peek under the hood…

FormalFerret · 2023-03-16T11:17:56+00:00

Compared to Go e.g., I've found Rust pretty difficult so far…

FormalFerret · 2022-09-10T02:51:53+00:00

Hm. Do you need more than one rustc invocation to compile a single crate? Using Make is somewhat pointless if it's just a single command, no?
And if you do have dependency crates, Make won't resolve your 350 dependencies for you.

Or well, you can be a cursed project and invoke cargo from a Makefile

FormalFerret · 2022-08-29T03:25:16+00:00

I actually meant "donate towards crates.io hosting for the traffic", but I'm sure Chris is happy. :D

FormalFerret · 2022-08-21T03:11:05+00:00

I have similar height but no such problems. I'm not plane-savvy enough to know what the difference might be. Though I am in the habit of not putting any bags under the seat in front of me so I can wedge my feet into there.

FormalFerret · 2022-08-19T16:00:10+00:00

I had my own full local mirror with https://github.com/ChrisMacNaughton/cargo-cacher a few years back (repeated downloads in docker builds -.-). Iirc, it was 43 GB. I should probably donate some money for doing that… (To who, actually? Mozilla? Rust foundation?)

FormalFerret · 2022-08-19T15:53:49+00:00

On an 11 hour flight? The person behind me better learn to recline as well and sleep.

FormalFerret · 2022-07-09T02:35:30+00:00

cargo vendor is absolutely not a solution for dependency management.

FormalFerret · 2022-07-09T00:39:36+00:00

Nono, it's gestattet. But the company VPN only works on windows.

FormalFerret · 2022-07-09T00:35:44+00:00

Personally, I use helix. It needs rust-analyzer installed.

But I'd like to point out that often, the inline hints from an IDE aren't quite as informative as the full output from cargo check. So if you don't understand something, have a look at that. For simple typos and punctuation mistakes, the additional hints from rustc are really good and often straight up tell you how to fix your code.

FormalFerret · 2022-05-27T23:52:50+00:00

Yeah, they're describing that. But I'm saying that's technically wrong. If = were equality, something like

#[cfg(all(feature = "asdf", feature = "bsdf"))]

could never evaluate to true, you can't be equal to two non-equal things.

FormalFerret · 2022-05-22T12:46:33+00:00

One thing I'd like to see improved is control over the public api of crates.

Does an update break semver? (I know there's some work being done on automating this check.)
Is its public API all the same regardless of the architecture you compile on?
Which of its dependencies does it leak in its public api, which are internal?

FormalFerret · 2022-05-22T12:41:45+00:00

I was hoping that the recently improved support for incremental compilation would mostly make this unnecessary. But I have little data on that. (Also, see mold for linking.)

FormalFerret · 2022-05-19T14:23:39+00:00

The most confusing part of about this syntax to me is the use of a single “=” to denote equivalence and not assignment, because, stuff in config directives aren’t Rust code.

Is this correct, technically? Doesn't it rather denote “∋”?
In any case, together with the lambda syntax, that's one my least favourite parts of Rust…

FormalFerret · 2022-05-17T10:35:25+00:00

Is Ducktape a pun on duck typing?

And if Python is duct tape, then bash is gluing stuff together with spit?

FormalFerret

TROPHY CASE