From: Orgad Shaneh <orgads@gmail.com>
To: cygwin@cygwin.com
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Takashi Yano <takashi.yano@nifty.ne.jp>
Subject: VS Code is missing a few characters when running launch task in Git Bash
Date: Fri, 27 May 2022 10:15:18 +0300 [thread overview]
Message-ID: <CAGHpTBK=NbN4DAzgJC-KrDMNYXBAxNYXDn7gCPrHGSNwXp+Z5g@mail.gmail.com> (raw)
Hi,
I'm using Git Bash as the default terminal in VS Code. Using Git for
Windows 2.36.1 with the latest runtime, based on cygwin 3.5.0.
I have a launch configuration that executes a Node.JS application in
the integrated terminal.
When I launch it for the first time, it spawns a new terminal and
works correctly (most of the time), but when the terminal is being
reused (and sometimes also for a new terminal), the command is missing
a few characters, so it fails.
These are the commands that are executed. The first one works, the
second one fails.
/usr/bin/env 'NODE_OPTIONS=--require
"c:/Users/orgads/AppData/Local/Programs/Microsoft VS
Code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.bundle.js"
--inspect-publish-uid=http'
'VSCODE_INSPECTOR_OPTIONS={"inspectorIpc":"\\\\.\\pipe\\node-cdp.17916-22.sock","deferredMode":false,"waitForDebugger":"","execPath":"C:\\Program
Files\\nodejs\\node.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\\Users\\orgads\\AppData\\Local\\Temp\\node-debug-callback-c34e93d552518e0a"}'
"C:\\Program Files\\nodejs\\node.exe"
.\\..\\node_modules\\mocha\\bin\\_mocha "--timeout 9999" -r
tsconfig-paths/register my-app.js
cd F:\\Projects\\MyFailingProject/prjct-directory/dist ; /usr/bin/env
'NODE_OPTIONS=--require
"c:/Users/orgads/AppData/Local/Programs/Microsoft VS
Code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.bundle.js"
--inspect-publish-uid=http'
'VSCODE_INSPECTOR_OPTIONS={"inspectorIpc":"\\\\.\\pipe\\node-cdp.17916-23.ock","dferedMode":fale,"waitForDebugger":"","execPath":"C:\\Program
Files\\nodejs\\node.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\\Users\\orgads\\AppData\\Local\\Temp\\node-debug-callback-cc2a4594562280e4"}'
"C:\\Program Files\\nodejs\\node.exe"
.\\..\\node_modules\\mocha\\bin\\_mocha "--timeout 9999" -r
tsconfig-pathsregister my-app.js
The follwing characters are missing (marking them with **):
"inspectorIpc":"\\\\.\\pipe\\node-cdp.17916-23.**s**ock","d**e**fe**r**redMode":fal**s**e
... -r tsconfig-paths**/**register my-app.js
Notice there is one block (starts on char 325), which is missing 4
characters (325, 332, 334, 346), and another character close to the
end of the line.
Another execution was missing:
"execPath":"C:\\Program
File**s**\\nod**e**js\\node.exe","onlyEnt**r**ypoint":fal**s**e,"autoAttachMode":"
and the same slash.
The terminal also auto-types the missing characters (sers/) in the
next line, without executing it (waiting for Enter). The characters
are the same in both executions (sers/), only taken from different
locations.
This issue started a few months ago. IIRC it was around the same time
I reported the misordered characters issue (last February), but I
can't tell for sure.
With 3.5.0, it happens less than before, but I still hit it once in a while.
Any idea what can cause this?
- Orgad
next reply other threads:[~2022-05-27 7:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 7:15 Orgad Shaneh [this message]
2022-05-27 7:59 ` Adam Dinwoodie
2022-05-27 8:06 ` Orgad Shaneh
2022-05-27 12:22 ` Orgad Shaneh
2022-05-27 12:43 ` Takashi Yano
2022-05-29 6:00 ` Orgad Shaneh
2022-06-30 22:02 ` Orgad Shaneh
2022-06-30 22:08 ` Orgad Shaneh
2022-07-01 14:14 ` Johannes Schindelin
2022-07-01 23:34 ` Takashi Yano
2022-07-02 23:17 ` Takashi Yano
2022-07-03 13:02 ` Orgad Shaneh
2022-07-03 23:40 ` Takashi Yano
2022-07-04 5:57 ` Orgad Shaneh
2022-07-05 3:17 ` Takashi Yano
2022-07-05 11:18 ` Orgad Shaneh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGHpTBK=NbN4DAzgJC-KrDMNYXBAxNYXDn7gCPrHGSNwXp+Z5g@mail.gmail.com' \
--to=orgads@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).