nandi/oripublic Fork 0
7895c1d1c9bb1048807dc04f7246dc456c47e025
Commits
Clone
git clone https://git.rickub.com/nandi/ori.git
git clone ssh://git@rickub.com/nandi/ori.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

forked from bots-garden/ori

🛟 Updated. ca7e020 · on 7895c1d1c9bb1048807dc04f7246dc456c47e025 · k33g · yesterday
2026-09-18-git-push-hang.md · 23 lines · 1.4 KBmarkdown
Blame HistoryOpen raw

2026-09-18 — First push to origin hangs

Where we stopped

main (34e69b5) has never been pushed; the remote repo bots-garden/ori on git.rickub.com exists but is empty. Diagnosis done, fix not applied — the user chooses.

Root cause

  • HTTPS remote + 401 on push + no keychain credential ⇒ git prompts for a password.
  • Sessions started from VSCodium's integrated terminal export GIT_ASKPASS=/Applications/VSCodium.app/.../askpass.sh, so the prompt goes to a VSCodium input box, not the terminal. From a non-interactive context (Claude Code Bash tool, scripts) it blocks indefinitely.

Options for the next step

  1. SSH remote (recommended, verified working):
    git remote set-url origin git@git.rickub.com:bots-garden/ori.git then git push -u origin main.
    The local key is already authorised; ssh -T git@git.rickub.com answers "rickub: this endpoint serves git only".
  2. Keep HTTPS: run GIT_ASKPASS= git push -u origin main in a real terminal, answer the prompts once; credential.helper=osxkeychain (global, /opt/homebrew/etc/gitconfig) will remember them.

Traps

  • macOS has no timeout; use perl -e 'alarm N; exec @ARGV' <cmd> to guard hanging git calls.
  • Killing a hung git push leaves git-remote-https + askpass.sh orphans (ppid 1); check with ps -axo pid,ppid,command | grep askpass and kill them.
  • Also push feat/acp-webapp if the branch history is wanted on the server (only main was in scope).
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
# 2026-09-18 — First push to origin hangs

## Where we stopped

`main` (34e69b5) has never been pushed; the remote repo `bots-garden/ori` on git.rickub.com exists but is empty. Diagnosis done, fix **not applied** — the user chooses.

## Root cause

- HTTPS remote + 401 on push + no keychain credential ⇒ git prompts for a password.
- Sessions started from VSCodium's integrated terminal export `GIT_ASKPASS=/Applications/VSCodium.app/.../askpass.sh`, so the prompt goes to a VSCodium input box, not the terminal. From a non-interactive context (Claude Code Bash tool, scripts) it blocks indefinitely.

## Options for the next step

1. **SSH remote (recommended, verified working)**:
   `git remote set-url origin git@git.rickub.com:bots-garden/ori.git` then `git push -u origin main`.
   The local key is already authorised; `ssh -T git@git.rickub.com` answers "rickub: this endpoint serves git only".
2. **Keep HTTPS**: run `GIT_ASKPASS= git push -u origin main` in a real terminal, answer the prompts once; `credential.helper=osxkeychain` (global, /opt/homebrew/etc/gitconfig) will remember them.

## Traps

- macOS has no `timeout`; use `perl -e 'alarm N; exec @ARGV' <cmd>` to guard hanging git calls.
- Killing a hung `git push` leaves `git-remote-https` + `askpass.sh` orphans (ppid 1); check with `ps -axo pid,ppid,command | grep askpass` and kill them.
- Also push `feat/acp-webapp` if the branch history is wanted on the server (only `main` was in scope).