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
During the implementation of Azure e2e tests with SQLite as database, the full scan test was constantly failing due to a database is locked error, mainly at the waiting until asset is found in riskiest assets dashboard and waiting until findings trends dashboard is populated with vulnerabilities steps.
Example: failed to get dashboard riskiest assets: status code=500: 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 query DB: database is locked
These errors were not present when testing with other cloud providers.
Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 14 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.
This issue has been marked stale for 14 days, and is now closed due to inactivity. If the issue is still relevant, please re-open this issue or file a new one. Thank you!
Description
During the implementation of Azure e2e tests with SQLite as database, the full scan test was constantly failing due to a
database is locked
error, mainly at thewaiting until asset is found in riskiest assets dashboard
andwaiting until findings trends dashboard is populated with vulnerabilities
steps.Example:
failed to get dashboard riskiest assets: status code=500: 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 query DB: database is locked
These errors were not present when testing with other cloud providers.
Checklist
The text was updated successfully, but these errors were encountered: