Full absolute path in a commit makes checkout fail

From: Youtian WANG <wangyoutian@msn.com>
Date: Jan 4, 2025, 14:21 UTC
Message-ID: <TYCPR01MB1173678128DCC128099726865AB162@TYCPR01MB11736.jpnprd01.prod.outlook.com>

In a commit of a public repo (which might still require a sign in using github account, etc, due to possibly the service maintainer's configuration):

https://gitee.com/whyyouteach/erg4eye/commit/f5e2c1ea25aaee24868a1790cf59ccd0a8288c3c

, a file of full absolute path (including the volume, also known as drive letter, in windows operating system) shows up:

C:\erg4eye_3\xiangxun23080202

; I'm not sure how that path gets into the repo, as this is a repo for a pack of students. Maybe it's due to a 3rd party tool, or a direct upload via the web page of the git service.  I noticed that in:

https://github.com/gitkraken/vscode-gitlens/issues/932

, some similar issues appeared involving a vsCode extension for git.

I cannot checkout outWith the above described commit; the error message is:

error: invalid path 'C:\erg4eye_3\xiangxun23080202'

My question is: 
1) Per git design, such full absolute is not allowed as it might be out of repo, right?
2) If it's done by a 3rd party tool which might be buggy, git.exe or the git server would bury the problem in the repo history as long as it's not checked out. As a git hosting service wouldnot bother to check it out, hence it will not be an issue with the server. But once it's cloned and that commit is checked out, an issue would emerge.  Is this understanding correct?

Thanks,

Youtian Wang