Skip to content

fix(dev): bash 3.2 compatibility for dev-instance-manager.sh#268

Merged
LuD1161 merged 1 commit intomainfrom
eng-177/fix-bash-compatibility
Feb 6, 2026
Merged

fix(dev): bash 3.2 compatibility for dev-instance-manager.sh#268
LuD1161 merged 1 commit intomainfrom
eng-177/fix-bash-compatibility

Conversation

@LuD1161
Copy link
Contributor

@LuD1161 LuD1161 commented Feb 6, 2026

Summary

  • Replaces declare -A (associative arrays, bash 4+ only) with plain variables and a case statement in scripts/dev-instance-manager.sh
  • macOS (even macOS Tahoe Version 26.2 ) ships with bash 3.2 by default, which caused just dev to fail with unbound variable errors
  • No functional changes — same port mappings and behavior, just compatible with all bash versions

Resolves ENG-177

Test plan

  • Run just dev on macOS with default bash 3.2 and confirm it starts without errors
  • Run just dev on a system with bash 5+ and confirm it still works
  • Verify port assignments remain correct (FRONTEND=5173, BACKEND=3211 for instance 0)

… macOS compatibility

The dev-instance-manager.sh script used `declare -A` (associative
arrays) which requires bash 4+. macOS ships with bash 3.2 by default,
causing `just dev` to fail with "unbound variable" errors. Replace
the associative array with plain variables and a case statement to
ensure compatibility across all bash versions.

Signed-off-by: Aseem Shrey <LuD1161@users.noreply.github.com>
@LuD1161 LuD1161 merged commit f100991 into main Feb 6, 2026
3 checks passed
@LuD1161 LuD1161 deleted the eng-177/fix-bash-compatibility branch February 6, 2026 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant