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
{{ message }}
This repository has been archived by the owner on Oct 14, 2024. It is now read-only.
In the UI, when entering the dashboard, we get the following error (taken from the UI backend logs): time="2023-10-04T08:08:10Z" level=error msg="failed to get riskiest assets for vulnerabilities: failed to get riskiest assets: failed to get assets: failed to get assets. status code=500: failed to get assets from db: failed to build query for DB: failed to build DB query from $filter: unable to directly extract field type complex, you might need a function like length() or to specify a specific field"
This comes from the ui-backend riskiest assets api.
It seems as the issue is thst its doing a filter summary/totalVulnerabiliies ne null and totalVulnerabilties is a complex type not a field so the new validation is blowing up. ne null might be a special case when we want to allow for comparison on objects as well as on fields.
Expected Behavior
No error occur.
Affected Version
vmclarity version v0.5.0
Steps to Reproduce
Deploy vmclarity in Azure (probably on all platforms) and enter the UI dashboard.
The text was updated successfully, but these errors were encountered:
akpsgit
changed the title
UI Failed to get riskiest assets vulnerabilties
UI Failed to get riskiest assets vulnerabilities
Oct 5, 2023
Description
In the UI, when entering the dashboard, we get the following error (taken from the UI backend logs):
time="2023-10-04T08:08:10Z" level=error msg="failed to get riskiest assets for vulnerabilities: failed to get riskiest assets: failed to get assets: failed to get assets. status code=500: failed to get assets from db: failed to build query for DB: failed to build DB query from $filter: unable to directly extract field type complex, you might need a function like length() or to specify a specific field"
This comes from the ui-backend riskiest assets api.
It seems as the issue is thst its doing a filter
summary/totalVulnerabiliies ne null
and totalVulnerabilties is a complex type not a field so the new validation is blowing up. ne null might be a special case when we want to allow for comparison on objects as well as on fields.Expected Behavior
No error occur.
Affected Version
vmclarity version v0.5.0
Steps to Reproduce
Deploy vmclarity in Azure (probably on all platforms) and enter the UI dashboard.
The text was updated successfully, but these errors were encountered: