GitLab context pull fails for repositories in subgroups

[florianehmann]

Describe the bug
When we add a (self-hosted) Gitlab repo that's located in a subgroup, Tabby fails to process the repo.

Information about your version
tabby 0.32.0

Information about your GPU
(we're using ollama to host the models)

Additional context
The following messages appear in Tabby's logs when the issue occurs:

tabby-1  | Cloning into '/data/repositories/https_gitlab.ourcompany.com_group-test_subgroup_stuff'...
tabby-1  | fatal: could not read Username for 'https://gitlab.ourcompany.com': No such device or address
tabby-1  | 2026-01-30T15:00:16.161066Z  WARN tabby_git: crates/tabby-git/src/lib.rs:101: Failed to clone `https://gitlab.ourcompany.com/group-test/subgroup/stuff`. Please check your repository configuration.

The error about the username could suggest that tabby tries to infer a username from the URL.

The repository is accessed via a repository access token, not a dedicated user account.

[zwpaper]

Hi @florianehmann , i have tested locally, and subgroup from gitlab works well.

as from the log you post,

fatal: could not read Username for 'https://gitlab.ourcompany.com/': No such device or address

it seems that tabby may have no network access, can you make sure you can clone the project manually on the node running tabby?