Gilles Querret
Gilles Querret
It is likely to come from a synchronization issue, such as analysis triggered while the AVM session was not connected to all sessions, or one DB was manually disconnected. It's...
Conversion from DECIMAL to INT can overflow: not reported in PDSOE when decimal returned from METHOD
Should be fixed with SonarLint 7.13 or 9.1. Could you check in your environment ?
Conversion from DECIMAL to INT can overflow: not reported in PDSOE when decimal returned from METHOD
Could this be related to this issue: https://github.com/Riverside-Software/sonar-openedge/issues/1105 ? Do you see the issue intermittently ?
Conversion from DECIMAL to INT can overflow: not reported in PDSOE when decimal returned from METHOD
It's in fact not directly related to the size of the file.
Conversion from DECIMAL to INT can overflow: not reported in PDSOE when decimal returned from METHOD
9.1.2906 generates `.sonarlint/rcc.txt` with the list of known classes, and passes a property to SonarLint with this filename. However, that was dependant on the status of the PDSOE code model....
Reproduced. Investigating root cause.
It could be possible to exclude a list of statements. There are really so many indentation styles when working with the preprocessor !
That's just in case you change to `exp(2, 31) + 1` 😄
The very first versions of this rule (not sure if that was part of the public release) reported those issues, but it was a bit too noisy on various codebases....
Cleaning up old issues, I assume it won't be fixed.