Andrew Baxter

Oh awesome! Okay, well in any case it would be good to get it fixed here too just in case someone else has the issue, and doesn't hurt to bump...

FWIW upstream was fixed, I think I've updated cargo-manifest now so I believe this has been resolved for a while.

Take this with a grain of salt, I'm exploring using a GC library but haven't committed to it yet. While my current project wouldn't have any issues with GPL I...

I had a typo and mine output an error to the terminal and exited... I assume this is the same issue: ``` [2024-08-17T04:54:06Z ERROR wgshadertoy::core] Validation error: "Validation Error\n\nCaused by:\n...

Ah yeah, thank you, of course, but the risk of a typo in your code shouldn't be a crash and a loss of all code. I assumed that was what...

+1 for an option to attach source locations to the tree. The generic tree parser in being generic loses some amount of type safety, requiring you to know more about...

`packet_size` appears to be broken: https://github.com/libpnet/libpnet/issues/519

Ah! It looks like the device UUID is available in udev: ``` ID_FS_UUID_SUB=2ecde329-a682-433d-88a3-68e164347d07 ID_FS_UUID_SUB_ENC=2ecde329-a682-433d-88a3-68e164347d07 ``` It's not linked on my system - is that used udev rules on common distros?

I see it referenced in `69-md-clustered-confirm-device.rules`: ``` PROGRAM="/usr/bin/blkid -o device -t UUID_SUB=$env{DEVICE_UUID}", ENV{.md.newdevice} = "$result" ENV{.md.newdevice}!="", RUN+="/usr/bin/mdadm --manage $env{DEVNAME} --cluster-confirm $env{RAID_DISK}:$env{.md.newdevice}" ENV{.md.newdevice}=="", RUN+="/usr/bin/mdadm --manage $env{DEVNAME} --cluster-confirm $env{RAID_DISK}:missing" ``` Unfortunately that's...

So I guess in summary: 1. Is this the expected way of identifying drives? 2. Could these be proposed as recommended udev rules?