Surface out of disk/memory error message for easier visibility

[honeyankit]

Context

These currently end up in the unknown_error category so this provides easier visibility to the user.

• Added out of disk error message to the go module updater.
• Added out of disk/memory error message to the yarn file parser.

[jakecoffman]

I'd bet the error message write fatal: sha1 file '/home/dependabot/dependabot-updater/repo/.git/index.lock' write error. is not coming from Go and Yarn CLIs, but our workspace/git.rb operations.

[honeyankit]

I'd bet the error message write fatal: sha1 file '/home/dependabot/dependabot-updater/repo/.git/index.lock' write error. is not coming from Go and Yarn CLIs, but our workspace/git.rb operations.

There are two errors in the sentry:
https://github.sentry.io/discover/deltaforce:b9cc2996e6104f6dbf95937df5aa4f68/?field=title&field=event.type&field=project&field=user.display&field=timestamp&field=replayId&homepage=true&name=All+Events&project=1451818&query=disk&sort=-timestamp&statsPeriod=90d&yAxis=count%28%29

One is from workspace/git.rb and another one from No space left on device @ io_write - yarn.lock. So is it the case that the issue is in workspace/git.rb and because of that yarn.lock is failing out of disk?

[jakecoffman]

write fatal: sha1 file '/home/dependabot/dependabot-updater/repo/.git/index.lock' write error appears to be coming from workspace/git.rb so I would catch it there, it won't be coming from Go or Yarn code that won't fix the issue.

I agree that No space left on device @ io_write - yarn.lock is coming from the Yarn file parser, that looks good 👍

[abdulapopoola]

Tagging @bdragon since he has context on the git.rb file ; he might have some context on that file and it might be the true source of the failures as @jakecoffman pointed out.

[abdulapopoola]

Took a peek - it appears the source of the failure is the reset command

[honeyankit]

Took a peek - it appears the source of the failure is the reset command

Yes, but I want to add exception to the common place where run_shell_command is defined. In the git.rb, the run_shell_command is called by different git operations and adding it there will make more sense. I have already pushed the change, just adding test and we are good!