Did you just expect people that call random devs at random times to actually read any information on a website?

Yeah they were experimenting with 64bit exploitation when this signal handler got some focus regarding a (likely related) deadlock so they rushed to disclose their findings to the project to minimise the possibility of having eyes on this vulnerability

I guess it’s also my bad. After reading the text with a more neutral mindset it’s not that clear cut as I initially read it. My bs detector tends to get a bit sensitive when AI comes up and I interpreted the wording in the worst way possible.

As the first AI-based mutation testing tool, Mutahunter surpasses traditional “dumb” AST-based methods. Our AI-driven approach provides a full contextual understanding of the entire codebase,

This is where I call bullshit. The AST is a precise representation of the code which should be easier to analyse and modify instead of the raw text. If you only rely on processing the text I have a hard time believing your AI has a deep understanding of the contextual interdependencies of the different parts of the code.

Edit: it kinda does use the AST if one of the preconditions is a treesitter grammar? Maybe the marketing wording is just very unfortunate?

Huh that might actually be an issue with your client, mine renders those as two dots

Hm it seems I misread the documentation there. I know why it doesn’t resolve the “…” and that’s fine, it just seemed very unnecessary in combination with my flawed understanding of the relative path handling.

Edit: and just to be snarky: I didn’t type “…” I typed “…”. ;)

I’m not really sure I get the usefulness of this absolute function. It still returns relative paths if the input was relative and it doesn’t resolve “…”. What would you use it for where canonicalize doesn’t work for you?

You don’t know that.

That’s not the tone I like to read even as an answer to a statement I don’t agree with. No need to get that personal.

I’m not saying nobody should work on this. There is obviously demand or at least big tech is assuming demand. I’m just saying it’s not surprising to me a lot of Foss developers don’t really care.

I think the biggest problem is that ai for now is not an exact tool that gets everything right. Because that’s just not what it is built to do. Which goes against much of the philosophy of most tools you’d find on your Linux PC.

Secondly: Many people who choose Linux or other foss operating system do so, at least partially, to stay in control over their system which includes knowing why stuff happens and being able to fix stuff. Again that is just not what AI can currently deliver and it’s unlikely it will ever do that.

So I see why people just choose to ignore the whole thing all together.

I guess but bios was a thing way before uefi and while it apparently also was a pain because people implemented it differently it did work.

Afaik the mein problem with arm is the discoverability of the hardware on the bus. For x86 it’s pretty dynamic but arm needs something called a device tree.

Especially with android I don’t get it. Every vendor has to maintain their own boot loader and modify the aosp code just to get it to boot on their devices. Is it just to avoid people slapping their own os on their phones?

I never understood why booting arm is such a pain. I mean I get that the current situation is that it is a pain but I don’t get why this is the situation.

This point advocates against the use of mod with content in a file unless it is used for a testing module. A common pattern is to have the unit tests for a module inside the main module file. Tests in rust are just specially tagged functions. To avoid compilation costs in non-test builds and false unused code warnings you can put all test related code in a submodule and tag that module with #[cfg(test)]. That way the module will only be included and compiled if the crate is being compiled to run tests.

The Star wars thing refers to scrolling long text files similar to the intro of the starwars movies where a long text is scrolled for the viewer.

mod name declares that the module should be compiled and reachable as a submodule of the current module. This assumes that you have a file or directory of the name in the right place. This is what you should do.

You can also declare a module like this: mod name {...} where you just put the content in the block. The two are functionally equivalent, from the compilers perspective.

I think you are missing the part where the community also gives back to the project. At some point the project isn’t really the creation of the original author anymore.

One good thing about zstd is that the main developer is full-time employed to work on it. Alas he’s employed by meta to do that… But it’s likely harder to social engineer your way into that project

Apparently it differs between distributions

No. I won’t not do that. For security reasons.