How to exclude or skip some line of code from Sonar violations

Exclude and skip any line of code from Sonar, so sonar will not run the violation check on that line of code. This could be done by adding a comment "//NOSONAR" at the end of line of code or block of code.

For example, in this code Sonar is raising Critical vulnerability, but this needs to be present in the code and something which cannot be changed. So, in this situation, to run the sonar successfully, this line of code should get excluded from Sonar violation check, and to do so, there will be a comment //NOSONAR needs to get added at the end of this line of code. 

e.g.

AlgorithmParameterSpec paramSpec = new IvParameterSpec(IVAes); //NOSONAR

Reference

https://www.baeldung.com/sonar-exclude-violations

Theory of Transformation or Evolution(Parinamavada) | Indian Philosophy

The Samkhya view is found in the famous words of the Gita (2.16): “There can be no existence of the non-existent and no non-existence of the existent.”
According to this view, an effect is not a new entity; an effect is already contained in its cause in an unmanifested state, and the production of an effect merely means its manifestation. Since an effect exists in its cause in an unmanifested state even before its appearance, it is considered to be ever-existent (sat), and hence the Samkhya theory of causation is called Satkaryavada (the theory of ever-existent effect). As the manifestation of an effect is brought about by a change in the cause, which is conceived as a real change, it is called parinamavada or vikarvada, i.e., theory of transformation or evolution from the cause.

SecureRandom random byte

Generates a user-specified number of random bytes. If a call to setSeed had not occurred previously, the first call to this method forces this SecureRandom object to seed itself. This self-seeding will not occur if setSeed was previously called.