failed to read configuration: mkdir C:\Windows\system32\config\systemprofile: Cannot create a file when that file already exists.
Checklist
-
I'm using the latest version of the extension (Run glab --version)- Extension version: glab version 1.30.0 (2023-05-19)
-
Operating system and version: Windows 11 -
Gitlab.com or self-managed instance? self-managed instance -
GitLab version (if self-managed) GitLab Enterprise Edition v16.0.5-ee (Use the versionendpoint, like this: gitlab.my-company.com/api/v4/version) -
I have performed glab auth statusto check for authentication issues
Summary
Summarized in title. To add detail:
glab.exe runs fine on my dev box. I need to run it on a server, and kick start it from a web service, running under IIS. When I do this it bombs with:
failed to read configuration: mkdir C:\Windows\system32\config\systemprofile: Cannot create a file when that file already exists.
surprising us all. No probs I'll have to use curl and the rest API. But glab.exe looks and feels portable and IMHO should be not bombing on some effort to create a system folder on a secured system. Tsk, tsk.
Steps to reproduce
Run it from an ASP .NET web app under IIS using the .NET Process libs. It runs fine (as do other things), just bombs with this error.
What is the current bug behavior?
This crash.
What is the expected correct behavior?
No crash. Do what I ask it to.
Possible fixes
It should fail gracefully and internally only recovering with a good fallback if it can't do whatever it's trying to do here. I'm only using it with the api command to interact with the API.
And yes, I'd rather do that from .NET but there's a unfortunate bug in .NET that makes it impossible to send REST api URLs. DIscussed here:
The upshot is because your API demand %2F encoded paths and the .NET libs url decode this before sending no-one has a working solution to do this. And I use the graphql API where I can but alas you do not make the datetime fo last commit fo a file available through the graphql API.