if the source dir for an mdbook contains the build output dir(?) we recurse infinitely #669
Description
failed to copy
./book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/FontAwesome/fonts/fontawesome-webfont.svg
to
book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/book/FontAwesome/fonts/fontawesome-webfont.svg
Reported to me over discord. I haven't looked fully into it and i'm not sure which copy is freaking out, but clearly something somewhere is trying to recursively copy a directory, and it's recursing into the directory where things are getting copied, so it just keeps digging itself deeper and deeper until something explodes. Apparently mdbook proper has some logic to avoid this.