ble.sh slow to start in recent versions

[Jai-JAP]

I am using ble.sh since a long time and recently the startup times are increasing, this is especially noticable in when using a debugger or some similar tools in VSCode.

The commands sent to the terminal are executed after a while as in the below video.
Recording 1
Recording 1 with ble.sh disabled

This is especially troublesome when actually debugging / running a file as the first command is not run (venv doesn't get activated at all). This behaviour is shown below.

See that in the video below the venv doesn't get activated at all.
Recording 2
Recording 2 with ble.sh disabled

This is still the issue on a older version of vscode and extensions and it vanishes when disabling ble.sh. It was not an issue until recently and was working perfectly fine.

[akinomyoga]

I am using ble.sh since a long time and recently the startup times are increasing,

Is that caused by changes in ble.sh? Or is the startup time increased by another factor? If it's the former, could you tell a commit without the issue?

Recording 2 with ble.sh disabled.

As far as I see this, VS Code seems to send ^C (C-c) after the source command, which cancels the execution of the command if the command hasn't been executed at the timing the shell receives ^C. Currently, it just waits for a fixed time and sends ^C, which I anticipate would cause a problem with any time-consuming ~/.bashrc, and thus it is not a problem specific to ble.sh.

This seems like an issue with the VS Code (or the related plugin). It should activate the virtual environment through --rcfile, or it should properly sequence the timing of the execution of the previous command and ^C.

[akinomyoga]

It is activated for sure. On the bottom right corner, it says 3.10.6 ('.venv'), and a tooltip pops up saying ./.venv/bin/python when I hover a mouse cursor on 3.10.6 ('.venv') on the bottom right corner.

Without ble.sh

With ble.sh

[akinomyoga]

In both cases, the virtual environment is not set up for the launched shell session.

On the other hand, as far as I use "Run Python File" (instead of "Python Debugger: Debug Python File"), the virtual environment is set up both with and without ble.sh.

[akinomyoga]

• What is your VS Code version?
• Also, what is your Python Extension version?

---

Here's mine.

Version: 1.96.2 (user setup)
Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f
Date: 2024-12-19T10:22:47.216Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

Identifier ms-python.python
Version 2024.22.1
Last Updated 2024-12-24, 16:44:34
Source VSIX
Size 47.5 MB
Cache 1.7 KB

[Jai-JAP]

Just did a bit more fiddling with the vscode configuration and it seems like the issue is indeed with the shell-integration breaking things. (They even mentioned that it breaks in complex situations)

https://code.visualstudio.com/docs/terminal/shell-integration#_automatic-script-injection

Now disabling the automatic loading of shell integrations and loading it manually seems to resolve the issue completely.

It is also the same if I completely disable the shell integration via the terminal.integrated.shellIntegration.enabled setting.

EDIT: Even after manually loading the shell-integration, it does not work at all with ble.sh. This is a completely different issue and VSCode cannot identify any thing within the terminal, not even commands, execution stauses, prompts etc.
At this moment, I would not bother waiting for this to fix as its barely a thing I use and went unnoticed since I started using ble.sh in VSCode. However it would be great to see ble.sh working flawlessly with VSCode and I am willing to help wherever possible in my available time.

Note: https://code.visualstudio.com/docs/terminal/shell-integration#_supported-escape-sequences

Please add to the docs/wiki mentioning that VSCode Integration is broken with ble.sh.

[Jai-JAP]

My VSCode version is

Version: 1.96.2
Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f
Date: 2024-12-19T10:22:47.216Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.12.6-arch1-1

Python Extension version

Identifier: python.python
Version: 22.1
Last Updated: 12-24, 13:09:04
Size: 5 MB
Cache: 0 KB

[Jai-JAP]

I got some time to fiddle with the config and finally got the manual loading of VSCode Shell Integration to work.

It needed adding the following lines to .blerc. (Transient Prompt enabled)

if [[ "$TERM_PROGRAM" == "vscode" ]]; then
  PS1_FINAL="\033]633;A\010\033[0m${PS1_FINAL}\033]633;B\010\033[0m"
  blehook PREEXEC+="echo -ne '\033]633;C\010\033]633;E\${1}\010\033[0m'; " \
    POSTEXEC+="echo -ne '\033]633;D;'\$?'\010\033[0m'; " \
    CHPWD+="echo -ne '\033]633;P;Cwd='\$(pwd)'\010\033[0m'; "
fi

bleopt prompt_ps1_final="$PS1_FINAL"

For Transient Prompt disabled instead, we need to add the following lines.

if [[ "$TERM_PROGRAM" == "vscode" ]]; then
  PS1="\033]633;A\010\033[0m${PS1}\033]633;B\010\033[0m"
  blehook PREEXEC+="echo -ne '\033]633;C\010\033]633;E\${1}\010\033[0m'; " \
    POSTEXEC+="echo -ne '\033]633;D;'\$?'\010\033[0m'; " \
    CHPWD+="echo -ne '\033]633;P;Cwd='\$(pwd)'\010\033[0m'; "
fi

[akinomyoga]

I took a look into the behavioral difference that I observed in #524 (reply in thread).

Thanks for the detailed setup. I could reproduce the problem. The problem arises with the following bashrc:

# bashrc
source /path/to/ble.sh
ble-attach

while it doesn't with the following bashrc:

# bashrc
source /path/to/ble.sh

This is unrelated to the speed of the initialization because I confirmed that the problem doesn't arise with the second setup no matter how slow the initialization is. Also, this is unrelated to the recent versions of ble.sh because I confirmed that the behavior is the same even in ble.sh of four years ago. So the initially provided information was mostly wrong guesses. Anyway, now that I could reproduce it in my environment, I can fix it on my side. Thanks.

It turned out to be caused by the VS shell integration. When one calls ble-update in the initialization file ~/.bashrc, ble.sh requires it to be at the end of the initialization script. However, VS Code terminal seems to use a different initialization file at xxxx/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh. Then, ~/.bashrc is manually sourced from that shellIntegration.sh. Then, shellIntegration-bash.sh modifies PS1 afterward. This breaks the requirement of ble.sh. Then, PS1 that ble.sh recognizes is not updated by shellIntegration-bash.sh, which caused the difference I found above.

However, your issue seems to be unrelated to this one because you reported that you don't have ble-attach in your setting, though this problem shouldn't happen when you don't have ble-attach.