-
Notifications
You must be signed in to change notification settings - Fork 1
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
Mapping Errors #11
Comments
This is what I see in your traceback:
I don't know why, but this error started popping up because the database stopped accepting null values for the file_type_id. I don't know why it started happening, but thankfully we don't ever need the file_type_id for our use case, so I changed the schema to allow null values for that item. Running the following command should fix the schema and get the database ready for a new set of scans:
It will reset the |
@Nebrethar : I want to make sure Augur controls the schema definition. So, if I reverse engineer the change you made in |
Just to be sure, I'm talking about the augur-spdx schema that is initialized when you install augur-spdx, or reinitialize the spdx schema. I'm not sure what That |
@Nebrethar : Got another, similar error. Same database as before, and it looks like it failed on the same repo. There seems to be an issue when it encounters a bitbucket repository. |
It fails on more than BitBucket. Here is the full list of URL formats it fails on:
This leads me to believe that augur-spdx only works on standard format |
The text was updated successfully, but these errors were encountered: