jseba

Results 19 comments of jseba

> Thanks for the explanation @jseba. > > > I used SIGUSR2 as the signal that firecracker gets from the OS on its parent's death > > Just to clarify,...

I fixed the merge conflict and rebased back onto the tip of main

> > No, the signal comes from the kernel directly, no other management process is involved. That's why I selected a different signal to differentiate it since otherwise it is...

Any update on the package story for 1.7? There's been 3 point releases so far for 1.7 and I don't see any packaging details for it. I'm willing to take...

cc @jacobbednarz @irvinebroque for review

@thaJeztah can we get packages cut for v1.6? It's still marked as the LTS and the latest version in the repos is v1.6.33; if v1.6 is not the LTS anymore,...

Furthermore, the executor interface never validates the information that it gets from the driver in CreateExecutor. It should be calling the Fallback NUMA scanner if it doesn't receive valid data...

Awesome, I'll give that patch a test this week and try to get a PR together with some tests soon if that goes well 👍

we were on release-20250820.0, which does not have those commits