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

Improved logging and error/exception processing and reporting #11

Closed
pombredanne opened this issue Jul 5, 2015 · 3 comments
Closed

Comments

@pombredanne
Copy link
Contributor

When running the scancode command, we should:

  • always capture expections and display formatted error messages
  • optionally have a way to log more details, such ass which file if being processed and for what
@pombredanne pombredanne modified the milestone: v2.0 Nov 5, 2015
@pombredanne pombredanne modified the milestones: v2.0, v2.1 Aug 5, 2016
@pombredanne
Copy link
Contributor Author

See also #364 and #365 to move errors to the file-level

@pombredanne
Copy link
Contributor Author

Errors are now properly captured including stacktrace details with the --diag option.

@pombredanne
Copy link
Contributor Author

We now always capture a full traceback since #885
Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant