You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cd distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT
./bin/connect-standalone.sh
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 37: [[: not found
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 41: [[: not found
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 84: [[: not found
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 37: [[: not found
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 41: [[: not found
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 87: [[: not found
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 93: [: Linux: unexpected operator
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 37: [[: not found
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 41: [[: not found
/rocketmq-connect/distribution/target/rocketmq-connect-0.0.1-SNAPSHOT/rocketmq-connect-0.0.1-SNAPSHOT/bin/runconnect.sh: 110: [[: not found
Root Cause: The error bin/runconnect.sh: 37: [[: not found indicates the script is being executed with /bin/sh instead of /bin/bash. The [[ conditional syntax is bash-specific and not available in POSIX sh.
Fix: Ensure the script is executed with bash:
bash bin/connect-standalone.sh
Or add a proper shebang line #!/usr/bin/env bash at the top of the script if missing.
Feedback Timeout\n\nNo feedback has been received on the proposed spec within 72 hours. The issue will remain open for community review, but the automated fix workflow is being paused.\n\nIf you'd like to proceed with this fix, please comment with:\n- /approve - Generate a PR for this fix\n- /revise - Request changes to the spec\n- /reject - Cancel this fix\n\nAlternatively, community members can submit their own PR to address this issue.
The script bin/runconnect.sh uses [[ (a bash-ism) but is executed with /bin/sh (which on many systems like Ubuntu/Debian is dash, not bash). The [[ construct is not supported in POSIX sh.
Root Cause: Missing #!/bin/bash shebang or script is invoked with sh instead of bash. The [[ conditional on lines 37, 41, 84, 87, 110 requires bash. Impact: Script fails to start on systems where /bin/sh is not bash. Severity: Medium — prevents Connect from starting on common Linux distributions.
Fix options:
Add #!/bin/bash shebang and ensure the script is invoked directly (not via sh runconnect.sh)
The error [[: not found indicates bin/runconnect.sh uses bash-specific syntax ([[) but is being executed by sh (dash on Ubuntu/Debian). The script shebang should be #!/usr/bin/env bash or the script should be invoked explicitly with bash.
Root Cause: Missing or incorrect shebang line, or script invoked with sh instead of bash. Impact: Cannot start connect runtime on systems where /bin/sh is not bash. Severity: Medium
Activity
RockteMQ-AI commentedon Aug 5, 2026
Issue Evaluation
Category:
bug| Status: ConfirmedRoot Cause: The error
bin/runconnect.sh: 37: [[: not foundindicates the script is being executed with/bin/shinstead of/bin/bash. The[[conditional syntax is bash-specific and not available in POSIX sh.Fix: Ensure the script is executed with bash:
Or add a proper shebang line
#!/usr/bin/env bashat the top of the script if missing.Automated evaluation by RockteMQ-AI
RockteMQ-AI commentedon Aug 8, 2026
Feedback Timeout\n\nNo feedback has been received on the proposed spec within 72 hours. The issue will remain open for community review, but the automated fix workflow is being paused.\n\nIf you'd like to proceed with this fix, please comment with:\n-
/approve- Generate a PR for this fix\n-/revise- Request changes to the spec\n-/reject- Cancel this fix\n\nAlternatively, community members can submit their own PR to address this issue.RockteMQ-AI commentedon Aug 10, 2026
Issue Evaluation
Category:
bug| Status: ConfirmedThe script
bin/runconnect.shuses[[(a bash-ism) but is executed with/bin/sh(which on many systems like Ubuntu/Debian isdash, notbash). The[[construct is not supported in POSIXsh.Root Cause: Missing
#!/bin/bashshebang or script is invoked withshinstead ofbash. The[[conditional on lines 37, 41, 84, 87, 110 requires bash.Impact: Script fails to start on systems where
/bin/shis not bash.Severity: Medium — prevents Connect from starting on common Linux distributions.
Fix options:
#!/bin/bashshebang and ensure the script is invoked directly (not viash runconnect.sh)[[with POSIX-compatible[testsAutomated evaluation by github-manager
RockteMQ-AI commentedon Sep 1, 2026
Issue Evaluation
Category:
bug| Status: ConfirmedThe error
[[: not foundindicatesbin/runconnect.shuses bash-specific syntax ([[) but is being executed bysh(dash on Ubuntu/Debian). The script shebang should be#!/usr/bin/env bashor the script should be invoked explicitly withbash.Root Cause: Missing or incorrect shebang line, or script invoked with
shinstead ofbash.Impact: Cannot start connect runtime on systems where
/bin/shis not bash.Severity: Medium
Automated evaluation by RockteMQ-AI