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

Better failure resilience in feature extraction #132

Open
rth opened this issue Mar 31, 2017 · 0 comments
Open

Better failure resilience in feature extraction #132

rth opened this issue Mar 31, 2017 · 0 comments

Comments

@rth
Copy link
Contributor

rth commented Mar 31, 2017

Currently when a single file fails to parse for some reason (the file path was not correct, the network storage was temporary unavailable, etc) the feature extraction process would stop with an exception. It would be better to catch the exception, continue the processing and at the end return the list of files that failed to parse (with the associated error messages).

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