{"thread":{"id":"59133","subject":"[BUG] `git stash` exits without output when lockfile present","startedAt":"2023-01-21T18:08:10Z","lastAt":"2023-01-21T18:08:10Z","messageCount":1,"participants":["Keith Layne"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"470843","messageId":"P0LUOR.9QAZEXOQT1VT1@laynes.org","threadId":"59133","inReplyTo":null,"subject":"[BUG] `git stash` exits without output when lockfile present","fromName":"Keith Layne","fromEmail":"keith@laynes.org","sentAt":"2023-01-21T18:07:37Z","receivedAt":"2023-01-21T18:08:10Z","isPatch":false,"sender":{"key":"keith@laynes.org","avatar":null},"body":"What did you do before the bug happened? (Steps to reproduce your issue)\n\nIn clean repo root:\n\n$ touch foo\n$ touch .git/index.lock\n$ git stash\n\nWhat did you expect to happen? (Expected behavior)\n\nAn error message to stderr explaining that .git/index.lock exists, etc.\n\nWhat happened instead? (Actual behavior)\n\n`git stash` has an exit code of 1, with no output on stdout or stderr.\n\nWhat's different between what you expected and what actually happened?\n\nI didn't notice at first that the stash failed, and I was briefly \nconfused. I guess I've never tried to stash and gotten this error \nbefore, but whenever I see the \"lockfile exists\" error I feel like the \nUX is very consistent with other commands. I expected stash to work the \nsame way.\n\nI apologize if this is a dupe, I don't know how to search the archives.\n\n\n[System Info]\ngit version:\ngit version 2.34.1\ncpu: x86_64\nno commit associated with this build\nsizeof-long: 8\nsizeof-size_t: 8\nshell-path: /bin/sh\nuname: Linux 5.19.16-76051916-generic \n#202210150742~1666053244~22.04~cf07008 SMP PREEMPT_DYNAMIC Tue O x86_64\ncompiler info: gnuc: 11.2\nlibc info: glibc: 2.35\n$SHELL (typically, interactive shell): /bin/zsh\n\n\n[Enabled Hooks]\n\n\n\n"}]}