You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is a bug or just an example of misuse that you don't really care if it exists.
Today I decided to copy all files inside of docs/ into docs/scratch-list so that I could test my app inside of my local instance before I deploy to https://falconmick.github.io/scratch-list/
about 10 seconds later I realised that somthing bad was probably happening and stopped the process. By this time it had created a directory 23108 characters long comprimised of 1775 sub directories of scratch-list.
At this point windows decided to be as awesome as possible and tell me that the files located inside of it had too long a name to delete, so I had to use robocopy to copy the files into oblivion (stupid I know).
For now my solution is going to be copy to a tmp dir then back into the docs/ folder after the prior one completes, but should this even be a thing? My thoughts would be it would copy the current files in that directory at time of start, not continuously look for new files.
Cheers,
Michael.
The text was updated successfully, but these errors were encountered:
I don't know if this is a bug or just an example of misuse that you don't really care if it exists.
Today I decided to copy all files inside of docs/ into docs/scratch-list so that I could test my app inside of my local instance before I deploy to https://falconmick.github.io/scratch-list/
about 10 seconds later I realised that somthing bad was probably happening and stopped the process. By this time it had created a directory 23108 characters long comprimised of 1775 sub directories of scratch-list.
At this point windows decided to be as awesome as possible and tell me that the files located inside of it had too long a name to delete, so I had to use robocopy to copy the files into oblivion (stupid I know).
For now my solution is going to be copy to a tmp dir then back into the docs/ folder after the prior one completes, but should this even be a thing? My thoughts would be it would copy the current files in that directory at time of start, not continuously look for new files.
Cheers,
Michael.
The text was updated successfully, but these errors were encountered: