I am lucky to have found this Debian package https://tracker.debian.org/pkg/similarity-tester (source https://dickgrune.com/Programs/similarity_tester/ ) to help me detect plagiarism in my students's C++ code. The tool is perfect as it gives side by side comparison of codes to help see if there's a really an issue. Usually, it is easy to confirm by spotting specific constructions or even the positions of punctuation in code. I have found something for Python though.
it's the opposite way round. png is especially good at compressing dithered images.
It's a reduced color palette, (in this case just black and white) so there's lots of repeated sequences. Which works very well with lossless compression.
First off... It's a system rescue tool... Have there been any massive advancements in the state of the art of system rescue in the past 8 months that need to be integrated into this tool?
Secondly, since this is void mklive based, whenever you run it, you get the current state of packages. This means that the actual programs are never really going to be out of date at time of building. The project would only need to be updated to update the few boot utilities which are included in the iso, or to update the LTS kernel included.
To add a little to that second part, I'd say this is really meant to be "built on your own", following that brief example at the end of the README. The releases are more of a convenience thing.
You will need Void's package manager XBPS installed, though. It can be harmlessly installed on other distros and won't (shouldn't?) interfere with the host package manager.
During a RCA, you find a specific error message associated with that incident. You deliver a new alert with some documentation about what it catches and what to do. You even generate automatically a ticket when it is raised.
Time passes.
There's a subtle change if the error message. You have another production incident but your alert hasn't fired.
The complexity comes from this: how do you know that an alert is still valid without creating an incident on purpose ?
It is mostly about the fact that if the variable is not static, then it's non-local to the translation unit and can be modified from everywhere else. So its value needs to be loaded and a plain and slow division is applied.
Having it local or const makes the compiler able to inline it and do a simple bitwise and with a constant.
So yes, make your variables static const by default (if you really need global).
They should not be allowed according to C.F.Date, but this is quite a controversial opinion. E.F.Codd who invented the relational model thinks nulls are fine.
