When calling for recent vulns, it just pulls everything from vulnerabilityaggregate table. Since our sources are increased, this started causing some memory overflow issues. We need to paginate the requests for recent vulns. Since there's only 10 CVEs shown on the page at once, it'd make sense to make additional requests upon navigating recent vulns.
This would require adjustments to the UI query calls as well, maybe add a page number parameter to indicate which 'page' (or day in this case) for recent vulns. We should also try to paginate the 'show more' portion, start with 100 CVEs on the current page, then just request more after by increasing the offset (or adjusting a num parameter that tracks the order, idk)
When calling for recent vulns, it just pulls everything from vulnerabilityaggregate table. Since our sources are increased, this started causing some memory overflow issues. We need to paginate the requests for recent vulns. Since there's only 10 CVEs shown on the page at once, it'd make sense to make additional requests upon navigating recent vulns.
This would require adjustments to the UI query calls as well, maybe add a page number parameter to indicate which 'page' (or day in this case) for recent vulns. We should also try to paginate the 'show more' portion, start with 100 CVEs on the current page, then just request more after by increasing the offset (or adjusting a num parameter that tracks the order, idk)