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.

Sign up for GitHub

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

Jump to bottom

Histories stored in wrong table #106

Closed
iamamoose opened this issue Jan 4, 2023 · 1 comment
Closed

Histories stored in wrong table #106

iamamoose opened this issue Jan 4, 2023 · 1 comment
Labels
bug

Comments

@iamamoose
Copy link
Contributor

Reported by email but creating an issue to remember it. Histories are being stored in the nvd_histories table instead of the right cve_histories or cve5_histories model table. So while histories appear to be working for new entries, histories from before 0.1.0 are not found/shown.

Note once fixed histories will need to be moved/merged out of the nvd_histories table.
@iamamoose iamamoose mentioned this issue Jan 4, 2023
Closed
@chandanbn chandanbn added the bug label Jan 4, 2023
@chandanbn
Copy link
Contributor

While this got fixed in code, a mongo script is needed to go through every _history collection and move the diff info and comments to the right collection to completely fix this.

raboof referenced this issue in raboof/Vulnogram Jul 10, 2023
@chandanbn @raboof
Fix apache#106 Histories in wrong collection
1c6dca8 
Cause: while refactoring doc.js in V1.0.0, one of the variables was global, which meant it pointed to the last document collection. Thats where all the document change histories went instead of the corresponding collection.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chandanbn @iamamoose