Why can't I clone the repository?

Question

git

after that
git clone https://github.com/r0-nook/R
produces

Cloning into 'R'...
remote: Enumerating objects: 2047, done.
remote: Total 2047 (delta 0), reused 0 (delta 0), pack-reused 2047
Receiving objects: 100% (2047/2047), 592.90 MiB | 1.74 MiB/s, done.
Resolving deltas: 100% (322/322), done.
error: invalid path 'R0_tail/n8/R1_Q8. Перекидыши. Крыса-2./фея/Фея.md'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

after that
git clone https://github.com/r0-nook/R ./
produces

Cloning into '.'...
remote: Enumerating objects: 2047, done.
error: RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054
error: 6407 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

discussion of the problem here https://stackoverflow.com/questions/22041752/githu...

Suggests that the problem is in access rights, if so then my question.
How to give this "permission"?

terminal, I open the PCM in the directory and select the horse in the drop-down menu, the system does not ask the question about opening with admin rights.

ps I just installed win10, I have one C drive and free 142GB

Answer 1

directories were created on linux in the names were superfluous points
to clone I tried on win10
Solution.
we go to the site ---
open the rap ---
go to the file lying in the directory with the "bad name" press the pencil and start editing. ---
at the top in the "address bar of the repository" put the cursor at the beginning of the file name and press the backspace until we get to the directory with the "bad name" - set the correct directory name = file ---
save the commit by pressing the button below ---
do this with each file located at this address ---
// I had only 2 files there and it did not become a problem
https://qastack.ru/programming/31861651/how-to-ren...

Answer 2

I suspect more that the path is curved. spaces, periods, Russian letters.
Maybe they pushed from Linux, but from Windows this path could not be inclined.
By the way, overly long names are discussed on Stackoverflow.
You can also check. Russian letters - in utf8 they take more bytes than English ones.
you can try
git config --system core.longpaths true or edit gitconfig (from admin)
or try tilting to a folder closer to the root of the drive.