This is very odd then. Why would project-files fail in the face of
(presumably) a perfectly well-behaved Git repository?
Pasting the backtrace here for Dmitry to have a look.
Test eglot-test-eclipse-connect backtrace:
string-match("\0" nil 0)
split-string(nil "\0" t)
project--vc-list-files("/tmp/eglot--fixturernYTOR/project/" Git nil)
#f(compiled-function (dir) #<bytecode
-0xa5be45661654310>)("/tmp/eglot--fixturernYTOR/project/")
mapcan(#f(compiled-function (dir) #<bytecode -0xa5be45661654310>)
("/tmp/eglot--fixturernYTOR/project/"))
#f(compiled-function (project &optional dirs) #<bytecode 0x114f4cd06dfc2088>)((vc Git
"/tmp/eglot--fixturernYTOR/project/"))
apply(#f(compiled-function (project &optional dirs) #<bytecode 0x114f4cd06dfc2088>)
(vc Git "/tmp/eglot--fixturernYTOR/project/") nil)
project-files((vc Git "/tmp/eglot--fixturernYTOR/project/"))
It would seem that the problem here is there are no files versioned yet,
so this expression in project--vc-list-files
(apply #'vc-git--run-command-string nil "ls-files" args)
Returns nil.
But I cannot reproduce this locally.