Readit News"If runsvdir receives a TERM signal, it exits with 0 immediately"
runsvdir receiving TERM should only happen when stage 2 is triggered to end.
Once that happens, the individual runsv processes are still supervising their individual tasks and can be requested to stop through their respective control sockets. It's how standard stage 3 is implemented.
Automating webroot is trivial and I would rather use an external rust utility to handle it than a module for nginx. I guess if you _only_ need certs for your website then this helps but I have certs for a lot of other things too, so I need an external utility anyway.
And no dns-01 support yet.
Remember the "Repeal the Online Safety Act" petition? It has gotten over half a million signatures and the response from the government was a loud "no".
> The Government has no plans to repeal the Online Safety Act, and is working closely with Ofcom to implement the Act as quickly and effectively as possible to enable UK users to benefit from its protections.
But I'm sure even if that happened, the public consensus would just be "good riddance".
This is an absolutely bizarre country to live in.
I'm not defending Microsoft, they are not necessarily my cup of tea, but these claims are only true of anything pre-Nadella era (part of 2014 and earlier).
Feel free to express your opinions, but don't be hateful!
They deserve plenty of hate.
I think it makes sense if you view it from a control theory perspective rather than an embedded perspective. The mechanics of the UI (be that a physical button or text input) create a flaggy signal. Naively updating the UI on that signal would create jank. So we apply some hysteresis to obtain a clean signal. In the day way that acting 50 times on a single button press is incorrect behavior, saving (or searching or what have you) 50 times from typing a single sentence isn't correct (or at least undesired).
The example of 10ms is way too low though, anything less than 250ms seems needlessly aggressive to me. 250ms is still going to feel very snappy. I think if you're typing at 40-50wpm you'll probably have an interval of 100-150ms between characters, so 10ms is hardly debouncing anything.
Interrupt pins are weird, level change too slowly? You might never see the interrupt trigger or you'll see it trigger more than once. Switch back and forth many times at a high frequency before settling? Again, you might see interrupts for every switch or you might just get nothing at all. (In summary, directly connecting a noisy switch to an interrupt pin will mean you can lose level transition events.)
To make this work reliably you either need to debounce in hardware before it reaches your interrupt pin or forego interrupts entirely in favour of polling the input pin at a specific speed and keeping a state history.
So the term as it originates in electronics is now both misused and if you do translate it back to electronics it's considered a terrible idea.
Remote: Yes (currently full time remote for 6 years, okay with going hybrid depending on distance)
Willing to relocate: No
Technologies: Linux/*nix, Rust/C/Python/..., low level (kernel contributor, also experienced in embedded), systems programming, back-end, have even done front-end but it's not my forte
Résumé/CV: https://kramkow.ski/cv.pdf
Email: tomasz@kramkow.ski
I've got at least some experience with practically everything you can imagine. I've spent the last 6 years in software-focused security but would like to get back to making (secure) things.
On a daily basis I encounter code written by people who have skills in one area and are trying to solve that problem within the context of another area they do not have skills in. These people will make poor decisions which are intended to solve problems I can easily imagine but which should have been solved a wholly different way.
As of yesterday (this started suddenly) any time Backblaze is performing a backup my whole system gets bogged down for no reason. Was fine days ago, so who knows what automatic update for what app caused it. It's probably an interaction with some other filesystem filter on my system, like Defender or Acronis True Image (which I am stuck using since every other disk imaging tool I've used is worse). Seeing this post on the front page has me wondering whether it's actually Backblaze's fault or it's Acronis, now...
I've previously tracked down random system freezes caused by some part of the NVIDIA driver interacting with one of my monitors, where the first unlucky process on my system to call certain graphics APIs after a boot or wake-from-sleep would cause the video driver to hold a lock and enumerate display modes for 10+ seconds. The end result was a "frozen" PC still responding to input, just unable to send new pixels to any of its displays. The fun part of that one was that profiling would blame these freezes on whatever user mode process was unlucky enough to make that graphics API call - Steam's browser overlay, Visual Studio's WPF rendering, the list goes on. The troubleshooting process for this one was expensive because I got to the point of replacing components before I figured it out.
I'm curious whether people who daily drive mac or linux encounter these sorts of system configuration gremlins. My experience using linux on servers and VMs has had some situations like this but I don't know whether the everyday experience just running Linux or OS X on bare metal is actually perfect at this point.
This is a privileged position as I am both a Linux expert, and an expert software engineer, and an expert troubleshooter/debugger. If you are not these things then I'm sure things don't work as well.