CommonCrawler
CommonCrawler copied to clipboard
More detailed logging upon failure(s)
trafficstars
Sometimes the network can fail or other things can happen... However, we don't have detailed logs for when a failure happens for a specific wet file... Would be nice to have detail logs in the output:
-
[x] Better logging for extract.go
-
[ ] Better logging for analyze.go
For more detailed logging I suggest to:
- replace CURL and gunzip calls with go code;
- return error values instead of books;
- move logging to higher level functions.
I made a pr #3 illustrating this ideas in code
@LastPossum thank you for the pull request. It has been merged... I will look into using more idiomatic error outputs when I do another push.