<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "bug" label: - https://gitlab.com/gitlab-org/cli/-/issues/?label_name%5B%5D=type%3A%3Abug and verify the issue you're about to submit isn't a duplicate. ---> ### Checklist <!--Please test the latest versions, that will remove the possibility that you see a bug that is fixed in a newer version.--> - [x] I'm using the latest version of the extension (Run `glab --version`) - Extension version: glab 1.92.1 (fcecef55) - [x] Operating system and version: Ubuntu 25.0 - [x] Gitlab.com or self-managed instance? _gitlab.com_ - [x] I have performed `glab auth status` to check for authentication issues - [x] Run the command in debug mode (like `DEBUG=true glab mr list`) and attach any useful output ``` `06:18:25 $ DEBUG=true glab auth status [git remote -v`] ``` ### Summary When trying to run a lot of commands, the client hangs and refuses to be killed w/ ctrl+c, forcing me to ctrl+z + kill -9. glab ### Environment <!--on POSIX system (Linux, MacOS), run bash -c 'printf -- "- OS: %s\n- SHELL: %s\n- TERM: %s\n- GLAB: %s" "$(uname -srm)" "$SHELL" "$TERM" "$(glab --version)"' and replace the following section with the result. If you use non-POSIX system, fill in the section manually: - OS: Your operating system including version and architecture (Windows 11 - AMD64, MacOS Sonoma - ARM64) - SHELL: Your shell (bash, fish, zsh, ...) - TERM: Your terminal emulator (Kitty, Xterm2..) - GLAB: result of running `glab --version` (glab version 1.32.0 (2023-08-18))--> - OS: Linux 6.14.0-37-generic x86_64 - SHELL: /bin/bash - TERM: tmux-256color - GLAB: glab 1.92.1 (fcecef55) <!--Please include any other information that you believe might be relevant in debugging. For example, you may include a shell framework like oh-my-zsh or other customizations like editing the prompt (PS1, PS2, and others).--> Other: The client worked for a bit when I first downloaded it, now it just hangs, I don't remember what happened. It think when I first installed glab, I authenticated fine, but accidentally selected ssh git cloning over https. Possibly when trying to clone a repo a few times and getting rejected, I got ipbanned or something, and now this behavior persists due to not handling some api call bans gracefully? Not too sure. Removing all of \~/.config/glab-cli does not do anything, the issue still persists ### Steps to reproduce On my local machine, running any of `glab auth status` `glab auth login` all hang. 06:23:48 \[✘148\] $ DEBUG=true glab auth login \[git remote -v\] \[git rev-parse --show-toplevel\] - Signing into gitlab.com \<hangs\> ### What is the current _bug_ behavior? Running glab auth login/status hangs ### What is the expected _correct_ behavior? It doesn't hang ### Relevant logs and/or screenshots ### Possible fixes <!--If you can, link to the line of code that might be responsible for the problem-->