{"thread":{"id":"63772","subject":"git bash bug","startedAt":"2025-07-09T17:20:25Z","lastAt":"2025-07-11T14:40:18Z","messageCount":3,"participants":["Preston, David J.","brian m. carlson","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"521709","messageId":"PH7PR11MB65466DEE20BA470C600C7B9B9549A@PH7PR11MB6546.namprd11.prod.outlook.com","threadId":"63772","inReplyTo":null,"subject":"git bash bug","fromName":"Preston, David J.","fromEmail":"david.preston@onegas.com","sentAt":"2025-07-09T17:20:22Z","receivedAt":"2025-07-09T17:20:25Z","isPatch":false,"sender":{"key":"david.preston@onegas.com","avatar":null},"body":"Bug report attached.\n\n\nThank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\nstarted happening after an update to a newer version of git... has been happening for a while, so i am not sure what version it started with\n\nWhat did you expect to happen? (Expected behavior)\nwhen using git bash in windows environment, when a previously typed command is executing and i start typing, i expect that what i type will eventually show up on the command line, in the order i typed it, once the executing command completes.\n\nWhat happened instead? (Actual behavior)\nletters that i have typed show up in a different order than i typed them.  basically, i think there is some async processing going on, and keyboard input is being handled in such a way that the keystrokes are output to the console in an order that is random based on race conditions in the async code.\n\nWhat's different between what you expected and what actually happened?\nkeys output in a different order than i typed them in.\n\nAnything else you want to add:\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.49.0.windows.1\ncpu: x86_64\nbuilt from commit: cca1f38702730b35f52c29efd62864b85e85ddcc\nsizeof-long: 4\nsizeof-size_t: 8\nshell-path: D:/git-sdk-64-build-installers/usr/bin/sh\nfeature: fsmonitor--daemon\nlibcurl: 8.12.1\nOpenSSL: OpenSSL 3.2.4 11 Feb 2025\nzlib: 1.3.1\nuname: Windows 10.0 22631 \ncompiler info: gnuc: 14.2\nlibc info: no libc information available\n$SHELL (typically, interactive shell): C:\\Program Files\\Git\\usr\\bin\\bash.exe\n\n\n[Enabled Hooks]\n"},{"id":"521721","messageId":"aG7xbbPf2ZsTh1ND@fruit.crustytoothpaste.net","threadId":"63772","inReplyTo":"PH7PR11MB65466DEE20BA470C600C7B9B9549A@PH7PR11MB6546.namprd11.prod.outlook.com","subject":"Re: git bash bug","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2025-07-09T22:47:09Z","receivedAt":"2025-07-09T22:47:12Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2025-07-09 at 17:20:22, Preston, David J. wrote:\n\nHi,\n\n> Thank you for filling out a Git bug report!\n> Please answer the following questions to help us understand your issue.\n> \n> What did you do before the bug happened? (Steps to reproduce your issue)\n> started happening after an update to a newer version of git... has been happening for a while, so i am not sure what version it started with\n> \n> What did you expect to happen? (Expected behavior)\n> when using git bash in windows environment, when a previously typed command is executing and i start typing, i expect that what i type will eventually show up on the command line, in the order i typed it, once the executing command completes.\n\nThe Git project doesn't ship bash, a terminal, or any software other\nthan the source code to Git.  Git Bash is part of Git for Windows, which\nis a separate project.  You may want to report this https://github.com/git-for-windows/git/issues.\n\nI would recommend searching for any relevant issues, open or closed,\nfirst and providing any information that might be relevant.  For\ninstance, does this problem only occur when the system is loaded or does\nit happen all the time, even with little load?  Is there anything else\ngoing on that is correlated with the problem (e.g., a virus scan)?  Does\nthe same thing happen when running Git for Windows's bash through\nWindows Terminal, or is it only the built-in MinTTY?  Those kinds of\nthings might help the maintainer solve the problem more quickly.\n\nBest of luck on this.\n-- \nbrian m. carlson (they/them)\nToronto, Ontario, CA\n"},{"id":"521817","messageId":"a8cfe8ee-81ab-b0e6-a82b-f8cbeb0d9122@gmx.de","threadId":"63772","inReplyTo":"PH7PR11MB65466DEE20BA470C600C7B9B9549A@PH7PR11MB6546.namprd11.prod.outlook.com","subject":"Re: git bash bug","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2025-07-11T14:40:03Z","receivedAt":"2025-07-11T14:40:18Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi David,\n\nOn Wed, 9 Jul 2025, Preston, David J. wrote:\n\n> What did you do before the bug happened? (Steps to reproduce your issue)\n> started happening after an update to a newer version of git... has been\n> happening for a while, so i am not sure what version it started with\n>\n> What did you expect to happen? (Expected behavior)\n> when using git bash in windows environment, when a previously typed\n> command is executing and i start typing, i expect that what i type will\n> eventually show up on the command line, in the order i typed it, once\n> the executing command completes.\n>\n> What happened instead? (Actual behavior)\n> letters that i have typed show up in a different order than i typed\n> them.  basically, i think there is some async processing going on, and\n> keyboard input is being handled in such a way that the keystrokes are\n> output to the console in an order that is random based on race\n> conditions in the async code.\n>\n> What's different between what you expected and what actually happened?\n> keys output in a different order than i typed them in.\n\nThis is essentially the same issue that has been reported at\nhttps://github.com/git-for-windows/git/issues/5632.\n\nThe problem is in the MSYS2 runtime, which is the POSIX emulation layer\nrequired to run Bash that Git for Windows employed, which in turn is a\nfriendly fork of the Cygwin runtime.\n\nI haven't had time to report this bug over in Cygwin yet (for which I\nwould have to verify that this bug reproduces with their own Bash running\nin their own MinTTY). Maybe you can help out and install Cygwin\n(https://cygwin.com) and perform that test?\n\nThanks,\nJohannes\n"}]}