I was collecting some data on the commits for a few projects using the c2dat map. The script had some bugs which should have been printed on the console. However, I was not able to see the error due to a barrage of messages like No 2646d3a48dfb64576a0cb9720fb2017578786276 in /fast/c2datFullU.
Since a missing commit in the dataset is not something a user can do anything about, I was wondering if it is worth putting a flag in getValues and showCnt commands for suppressing such error messages due to missing data. That would make it easier to spot other errors that might be fixed by the user. The attached screenshot shows how it looks like - I had to redirect the stderr to a file and delete the lines matching this pattern to see the actual error messages, which is a lot of extra work.
I was collecting some data on the commits for a few projects using the
c2datmap. The script had some bugs which should have been printed on the console. However, I was not able to see the error due to a barrage of messages likeNo 2646d3a48dfb64576a0cb9720fb2017578786276 in /fast/c2datFullU.Since a missing commit in the dataset is not something a user can do anything about, I was wondering if it is worth putting a flag in
getValuesandshowCntcommands for suppressing such error messages due to missing data. That would make it easier to spot other errors that might be fixed by the user. The attached screenshot shows how it looks like - I had to redirect thestderrto a file and delete the lines matching this pattern to see the actual error messages, which is a lot of extra work.