qube | virtual office that enables you to work | Collaboration library

-x and --command are incorrect/obsolete options, try this :

I suppose, the fact that you have a conditional like getElement(Details, null, "AMB") != null hints to the code audit tool that the method getElement may return null. In that case, the actual implementation code of the invoked method is not relevant.

Therefore, the tool produces a warning because the subsequent getElement(Details, null, "AMB").getTextContent().trim() dereferences the result of a call to getElement without a null check.

You seem to assume that two subsequent invocations of getElement(Details, null, "AMB") will return the same result, hence, the preceding test is sufficient, but code audit tools normally do not make such an assumption.

The simplest way to fix this, is to use a local variable to hold the result, which is generally to prefer over repeating expressions.

First of all, this Sonar rule was added about 2 years ago in this Pull Request with this example

I then found those SO articles answering similar questions: article 1, article 2 but it was still unclear to me so I kept on looking.

Finally I reviewed this documentation and found the answer I was looking for in the last example provided.

In the above example, notice there is no await statement after the return keyword, although that would be valid too: The return value of an async function is implicitly wrapped in Promise.resolve - if it's not already a promise itself (as in this example).

Note: The implicit wrapping of return values in Promise.resolve does not imply that return await promiseValue is functionally equivalent to return promiseValue.

I tried the error handling with and without the await on my project and ended up removing the await triggering the warning. So far I haven't seen any difference. I have also noticed that if you wrap the same code inside a try / catch, the Sonar warning isn't raised anymore.

From now on, I will follow Sonar's advice but will update this thread if I encounter an issue.

We cannot do this now, In the azure DevOps, we could see the Sonar report in the Sonar site.

You could add your request for this feature on our UserVoice site, which is our main forum for product suggestions. And produce team will check the request. Thank you for helping us build a better Azure DevOps.

Ok. It occurs this is "by design" SonarQube behavior. Details and methods how to overwrite it may be found on: https://github.com/SonarSource/sonar-scanner-msbuild/wiki/Analysis-of-product-projects-vs.-test-projects

To sum-up all suggestions from the comments:

Your main problem is:

• When you create the numbers list you use number = int(number/10). This changes the number variable itself until it is equal to zero. This means that, as you experienced, result == number will always be False.

Some redundant parts of your code:

1. See Splitting integer in Python? to get a list of a number's digits. Most commonly you can just do numbers = [int(i) for i in str(number)]. This will actually solve the problem above as you don't change number this way.

2. The digits are already integers so no need for an int conversion. It is also more readable to use direct loop in Python rather than looping over indices:

When fork is executed, the process executing it (the new parent) is executing (of course), and the newly created child is not. For the child to run, either the parent must be stopped and the child given the processor, or the child must be started on another processor, which takes time. Meanwhile, the parent continues execution.

Unless some unrelated event occurs, such as the parent exhausting the time slice it was given for sharing the processor, it wins the race.

You can suppress specific warnings by using @SuppressWarnings("squid:S00XX") where S00XX is a Sonar issue ID. You can find this ID in the Sonar UI based on your error or warning.

For suppressing multiple warnings you can try like @SuppressWarnings({"squid:S00X1", "squid:S00X2"}) i.e. provide multiple Sonar issue IDs.

Or you can also use //NOSONAR comment that tells SonarQube to ignore all errors for a specific line.

It appears you have not installed any language plugins in SonarQube (not Jenkins).

org.sonar.scanner.rule.QualityProfiles: No quality profiles have been found, you probably don't have any language plugin installed. -> [Help 1]

As a SonarQube Admin, log into SonarQube. From the main menu, Administration | Marketplace ..., filter on "Languages" for Sonar provided languages, "External Analyzers" for third party. "Install" as necessary, Restart required.

As of 7.X, SQ will analyze all code for which a language analyzer is installed; language=java is ignored.