Skip to content
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

Update --minutes-ago does not appear to work correctly if an update has already occurred we issued this update #22

Open
athu-tran opened this issue Jun 15, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@athu-tran
Copy link

Steps to reproduce:

  1. Manually ran Update action
  2. Manually ran Update action--minutes-ago 2880 (we did not get all of the CVE changes in the last 48-hours)
  3. Manually ran Update action--minutes-ago 4320 (we did not get all of the CVE changes in the last 72-hours)

Verify that the utilities is working correctly and the resulting /cves directory has the correct CVEs by running rebuild command

@hkong-mitre
Copy link
Collaborator

This is a concern if there are no updates in github for a long period of time (e.g., 24 hours), as was @athu-tran's case, where she forked the project, but did not enable the actions.

When debugging this, if the /cves directory isn't missing any CVEs, then the update command is working correctly, and the problem lies with the deltas called after update.

@hkong-mitre hkong-mitre added the bug Something isn't working label Jun 15, 2023
@hkong-mitre
Copy link
Collaborator

As a temporary work-around, you can use --before <timestamp> instead of --minutes-ago <minutes>. That will provide the same result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants