You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement the Paligo scanner from inside Checkmarx and run it in parallel with the current implementation in Checkmarx to compare the results and replace it.
The text was updated successfully, but these errors were encountered:
- get folders and components
- handle only `component` and `folder` types
- send content to items
- avoid reaching the rate limit
Note we are handling only `folder`s to find sub-folders or `components`,
and reading only the `component` (document) content.
### Rate Limit
The rate limit **per minute** described
[here](https://paligo.net/docs/apidocs/en/index-en.html#UUID-a5b548af-9a37-d305-f5a8-11142d86fe20).
The core lib `time/rate` is limiting the rate **per second**. That's why
I'm starting with open seats for all the requests-per-minute, in case
there are fewer requests than the limit. After the first
too-many-requests error, I'm reducing the available seats to 1, so the
frequency of the requests will not reach the rate limit.
Close#75
Implement the Paligo scanner from inside Checkmarx and run it in parallel with the current implementation in Checkmarx to compare the results and replace it.
The text was updated successfully, but these errors were encountered: