False Positive in Methods return value

[asd_asdasd]

Hi team,

We got an issue with sonar. It shows that we always return the same value but we do not.
As the screenshot below, we return 2 different boolean values (true/false).

[Colin]

Hey there.

Please provide an unredacted snippet of code that can reproduce the issue. A screenshot/description is not quite enough.

How to Report a False-positive / False-negative

Hey SonarSource Community! False-positives happen, as do false-negatives, and we’re eager to fix them. We are thrilled when our users report problems, so we can make our products better. What is a false-positive (FP)? A false-positive is when an issue is raised unexpectedly on code that should not trigger an issue, or where the suggested action doesn’t make any sense for the code. What is a false-negative (FN)? A false-negative is when an issue should be raised on a piece of code, but isn’t…

[asd_asdasd]

Hi @Colin ,

Here is the code snippet with redacted sensitive info.

[Colin]

Hey there.

We really need text, not a screenshot.

[asd_asdasd]

Here is the code.

    @Override
    public boolean preHandle(HttpServletRequest request, HttpServletResponse response, Object handler)
      throws Exception {
    if (!idempotencyService.isRequiredIdempotentCheckRequest(request)) {    
        return true;
    }
    String uId = channelRequestHolder.getUId();
    UUID idemKey = channelRequestHolder.getIdempotentKey();
    validateMissingIdemKey(idemKey);
    Optional<TransferIdempotencyRequest> previousRequestOpt =
        idempotencyService.findDuplicatedRequest(idemKey, uId);
    if (previousRequestOpt.isPresent()) {
      TransferIdempotencyRequest previousRequest = previousRequestOpt.get();
      if (!channelRequestHolder.isRequestEqualTo(previousRequest)) {
        //multiple requests with different parameters but the same idem key
        throw new IdempotentException(ErrorCode.PARAMETERS_MISMATCH);
      }
      //return memoized response directly without processing more
      writeMemoizedResponse(response, previousRequest);

return false;
    }
    
return true;
  }
}

[Dorian_Burihabwa]

Hi @asd_asdasd,
Thank you for sharing this bit of code as text, it makes our job a lot easier this way.

S3516 is a symbolic execution rule that sometimes is confused when evaluating possible execution paths that are conditioned with Optional.isPresent().

Unfortunately, I am having a hard time reproducing the issue with the code you shared in this thread as I am missing some of the logic (fields, methods, external classes, library versions, …)

Could you share a self-contained piece of code that produces the same false positive in your project?

Best,

Dorian