Bugfix: explicit directory creation for plugin outputs #3348
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
blueridger
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Users are getting blocked by the error
[Error: ENOENT: no such file or directory, open '/home/runner/work/makerdao-cred/makerdao-cred/output/graphs/sourcecred/discourse/graph']because our code is not running mkdir for plugin output directories. This bug didn't show in testing because on our dev laptops we were just overwriting within existing directories from a gh-pages clone rather than a fresh checkout of the main branch. This PR fixes the bug, making it so that the mkdir method is called down the directory chain before interacting with all plugin output directories.Test Plan