Attempting to delete a corrupted proposal will return the following errors:
sqlalchemy.orm.exc.UnmappedColumnError: No column repository_files.id is configured on mapper mapped class RepositoryFileComments->repository_file_comments...
sqlalchemy.orm.exc.UnmappedColumnError: Can't execute sync rule for source column 'repository_files.id'; mapper 'mapped class RepositoryFileComments->repository_file_comments' does not map this column. Try using an explicit foreign_keys collection which does not include destination column 'repository_file_comments.repository_file_id' (or use a viewonly=True relation).
As there is only one such entry and it's impossible to create new entries with a non-GitHub repository URL the quickest fix is to add the guard as described above.
Describe the bug Currently, when trying to propose changes for entries like https://www.vulncode-db.com/CVE-2014-0160 a corrupted proposal entry will be created. This is due to a lack of support for custom (non-GitHub) repository URLs like http://git.openssl.org/gitweb/[...].
Attempting to delete a corrupted proposal will return the following errors:
foreign_keyscollection which does not include destination column 'repository_file_comments.repository_file_id' (or use a viewonly=True relation).As there is only one such entry and it's impossible to create new entries with a non-GitHub repository URL the quickest fix is to add the guard as described above.