tmp:create creates the same dirs that tmp:clear removes #48057
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.
After running tmp:clear, tmp:create should ensure the same folders that are cleared are created.
Motivation / Background
This Pull Request has been created because the current tmp:clear and tmp:create tasks are opposites of each other, but do not currently affect the same directories.
tmp:clear
presently clears cache, sockets, screenshots and storage, buttmp:create
only creates the directories for cache, sockets, and pids.Thus there is some incongruency between
tmp:clear
andtmp:create
. Runningtmp:create
, for instance, does not result in atmp/storage/
directory and thus any ActiveStorage tests must create the directory themselves.Detail
This Pull Request changes the
tmp:create
rake task to additional ensure screenshots and storage directories are created.Additional information
Checklist
Before submitting the PR make sure the following are checked:
[Fix #issue-number]