Bash integration issues after upgrade to Build 3.5.0beta7

Bug report

• iTerm2 version: Build 3.5.0beta7
• OS version: 12.6 (21G115) / "Monterey"
• Attach com.googlecode.iterm2.plist here (drag-drop from finder into this window)
• Attach a debug log, if possible: debuglog.txt.gz
• Attach a screen capture video if it would make the reproduction steps clearer.

Detailed steps to reproduce the problem

1. Update iTerm2 to Build 3.5.0beta7

2. Run a couple shasum -a 256 piped commands w/subshell to compare files

3. Observe that iTerm2 now shows red-herring bash errors:

    133;C;133;C;133;C;133;C;133;C;133;C;133;C;133;C;133;C;133;C;133;C;-bash: umask: `: invalid symbolic mode operator
    -bash: umask: `: invalid symbolic mode operator
    sakai.echo360qa.org/sakai.echo360qa.org.crt: OK
    sakai.echo360qa.org/sakai.echo360qa.org.csr: OK
    [...SNIP...]
    shasum: WARNING: 1 line is improperly formatted
    0

What happened

Bash syntax errors that were never previously shown are somehow generated.

What should have happened

No bash syntax errors should have been shown. All .bashrc, .bash_profile, and .bash_it/* files have proper syntax and never produced errors before the upgrade. They have not changed since the upgrade.

Additionally, I ran set -x; and set +x; before and after the command which produced the 'red-herring' syntax errors. When showing all the bash command lines that are running for PS2 prompt & pre-exec hooks, no syntax errors appear. 👻

🤔 This appears to be some kind of timing, or race condition issue, or perhaps is related to iTerm2's .iterm2_shell_integration.bash interaction with the new build of iTerm2. It could also be that iTerm2 is mangling some background commands that bash is running? Not exactly sure, but just a hunch. 🤷

Bash trace log with set -x; ... ; set +x wrapping the command line: bash_set+x_trace.log.gz

---