Its not caused by the fact that windows does not support symlinks ( at least not like linux ) just guessing.

dunno

the exception seems to happen when trying to relativize a file which is from a different root (which means, I think, on Windows: from a different drive, e.g. c:/dude and d:/dude )

also, Windows 11 and Windows 10 both support symbolic links I read on some webpage. So the issue could be that on CI some .gitlib folder really lives on a different drive, which then causes the above problem

but this is damn hard to verify without my windows pc

You are beyond my understanding - hope you find a fix and/or fixer.

Perhaps someone with Windows can at least try to run the bbin tests locally to see if they get the same exception locally (with a new version of bb)

@U04V15CAJ you can run GHA tmate action in windows and shell in

aha, let me check that out, thanks

https://github.com/marketplace/actions/debugging-with-tmate

thanks, I'm in. And as I was suspecting, the path here starts with /d/.. while some other stuff is on /c/.. and thus you can't relativize the path

also my PC started working again. Just a break solves about everything it seems

I've fixed the problem in bb but now I'm trying to get a custom bb installed on Windows. How the heck do I add this binary to the Windows path. This fails: https://github.com/babashka/bbin/actions/runs/8852919505/job/24312593493

ok, hacked that this way: installed bb using github actions and then in shell bash under windows:

cp bb.exe "$(which bb)"

and confirmed that the fix fixed the issue. boy oh boy, this Windows issue took my entire day... good weekend everyone

thanks for that tmate action, that was gold

You're very welcome. Glad I could help you a tiny bit for all the help you've given me.