-
Notifications
You must be signed in to change notification settings - Fork 82
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
Migrate the ProjectError model to a more global ProjectMessage #338 #338
Comments
|
They cannot be created as packages (only resources) at the DB level since those are missing mandatory fields... |
Packages that are incomplete can or cannot be created (may be they could) when they are missing some key fields BUT in all cases these are warnings and not errors. I suggest these updates
could be resolved automatically as "not important" as this is a large (15MB) JSON data files that times out, adn is further a test file. Also it would be useful to:
There also bugs and improvement issues to have fewer errors and messages: |
Signed-off-by: Thomas Druez <tdruez@nexb.com>
Signed-off-by: Thomas Druez <tdruez@nexb.com>
Signed-off-by: Thomas Druez <tdruez@nexb.com>
Signed-off-by: Thomas Druez <tdruez@nexb.com>
Those Project issues are not particularly useful and there's often too much of those.
It has the bad effect of hiding more important errors that happened during pipeline runs.
@pombredanne any good reasons to keep creating those?
The text was updated successfully, but these errors were encountered: