Log the message and continue with next on error

[coni2k]

Fixes #437

Command for CSV output

go run .\cmd\criticality_score -gcp-project-id=[Project ID] -out=".\output\output.csv" ".\output\repos.txt"

The new CSV output after the update

repo.url,repo.language,repo.license,repo.star_count,repo.created_at,repo.updated_at,legacy.created_since,legacy.updated_since,legacy.contributor_count,legacy.org_count,legacy.commit_frequency,legacy.recent_release_count,legacy.updated_issues_count,legacy.closed_issues_count,legacy.issue_comment_frequency,legacy.github_mention_count,depsdev.dependent_count,__config_scorer_pike_depsdev_score
https://github.com/404/repo-not-found,,,,,,,,,,,,,,,,,NaN
https://github.com/babel/babel,TypeScript,MIT License,42433,2012-09-24T08:48:45Z,2023-08-02T22:03:56Z,132,0,1133,9,10.81,48,15081,14285,1.99,128779,8300887,0.87117

The output doesn't mention the error message; the user can check the console to see the details.

Alternatively, we could add a new field (Status?) that mentions the details ("OK", "Error: [Error message]").

And, there is one more "os.Exit(1)") at line 239, which might be handy to remove.

[sttor]

are we planning to add this check anytime soon?

[Carmendelope]

Have you considered moving directly to the next repository without adding an entry with the information of the one that failed (We could continue processing the output files without having to modify anything.)

Just changing the return by a continue

On second thought I think your solution is better

[Carmendelope]

any news about this?