Put all notifications to silent, except for the calls. Explain to everyone that, to get your immediate attention they have to call you. Look at your (now silent) messages when you have spare cycles (in between the focused sessions).
Is there a NixOS tool that can retroactively record what I did and translate the changes into the config file or do I have to write down each and every change manually again and again?
It’s generally best to make the change in your configuration.nix or flake.nix rather than with the imperative tools. Then you just version control that file (or files if you break it up)
Temperatures monitoring will be added. Initially, I implemented too many metrics, so during development I limited them to a reasonable level to make them manageable, but I'll be adding more as the project matures. Thanks for the feedback!
If you have a moment, I would be grateful if you could create an issue on github. I will then be able to let you know when it's ready and ask you to try it out. Please also let me know which temperatures you'd like to primarily monitor. I assume I'll have to gradually introduce the supported ones, as not all of them can be detected at once.
Sure thing. In my experiences based on using LibreHardwareMonitor [1] on Windows, and Dunnart [2] on Linux, dealing with temperature monitoring is not trivial. But it's not impossible either. For example, in Linux, looking at /sys folder for CPU temperatures, I can often find several entries, of which, some are dead, some are way off, and some are correct, but it is always a hit and miss endeavour. So, reliably monitoring temperatures requires a bit of an algorithm to detect the right source.
Yeah, that's a pain. Every time I boot up new hardware, I wonder how many readings I'll be able to get this time, and if it's even possible. On one computer, I have practically all the temperatures, voltages, and fan speeds, while on another, I can barely read the CPU temperature alone. Not to mention the need to sometimes compile sketchy drivers from github...
Fair question! NOVA is built on a different structural foundation. We operate as a terminal native execution layer designed to interact with your codebase and file system through a proprietary approach. It is really a difference in engineering philosophy because we focus on autonomous system level changes rather than standard session based history management.
both do if you can run python in WSL. I'm running both server and agent on a windows test machine, but I admit I'm not a windows user... also pro is free until May, so don't worry about costs. You can always hit me up for a free key after that though, I'm pretty loose about it.
reply