-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception thrown since presidio analyzer is in bad state #147
Comments
Hey @StefanKarlsson321 , I see that even this library is not doing a good jon on your prompt |
Hmm, but I get this. It seems to point to Presidio:
|
I see now but this issue is a bit different. We rely on the text replacer from the Presidio library, and apparently we didn't refresh credentials each time we run scanning. I fixed that issue in the latest commit. |
I added an Anonymizer after the secrets scanner, and got this from presidio_analyzer with the otherwise same code:
Will check and come back with updated presidio_analyser as well. |
When I update the presidio_analyzer to the very latest origin/main, then it seem that the issue is gone. Thanks a lot! |
Describe the bug
InvalidParamException exception thrown since presidio analyzer is in bad state
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No exception thrown and no secrets detected in the "Hello" prompt.
Screenshots
raise InvalidParamException(err_msg)
presidio_anonymizer.entities.invalid_exception.InvalidParamException: Invalid analyzer result, start: -1 and end: 63, while text length is only 5.
Additional context
Inspiration to finding bug: microsoft/presidio#1376
Although I have applied the fix related to the bug: microsoft/presidio#1377, the issue still occurs.
The text was updated successfully, but these errors were encountered: