Исправлен расчет конечного указателя. #69
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
При расчете конечного указателя к начальному указателю прибавлялась длина искомой строки. При этом, если искали всю строку, то начальный указатель был равен 1 (результат СтрНайти), а конечный указатель получался равен длине строки + 1 и указывал за пределы строки. Сонар-сканер при захвате такой выгрузки в режиме "genericissue"падал с ошибкой "java.lang.IllegalArgumentException: is not a valid offset for pointer"
После исправления сонар-сканер подхватил результаты АПК и они корректно отобразились в отчете на сервере.