Skip to content

Fix local setup on macOS: stale seed path and bash 3.2 incompatibility - #372

Merged
tomvothecoder merged 2 commits into
E3SM-Project:mainfrom
rajeeja:rajeeja/fix-local-setup
Oct 7, 2026
Merged

tomvothecoder merged 2 commits into
E3SM-Project:mainfrom
rajeeja:rajeeja/fix-local-setup

Conversation

@rajeeja

@rajeeja rajeeja commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Description

setup-local invoked app/scripts/seed.py, which moved to app/scripts/db/seed.py in
#105; || true hid the error so setup reported success with an empty database. Separately,
${DRY_RUN,,} needs bash 4+ and fails make backend-test on macOS (bash 3.2). One-line fix
each, separate commits.

Checklist

  • Code follows project style guidelines
  • Self-reviewed code
  • No new warnings
  • All tests pass (locally and CI/CD)

Deployment Notes (if any)

None. Chrysalis and CI run bash 4+, where behavior is unchanged.

The seed script moved from app/scripts/seed.py to app/scripts/db/seed.py
in E3SM-Project#105, but setup-local still invoked the old path. The trailing `|| true`
hid the resulting "No such file" error, so setup-local reported success
while leaving the database empty.

Reuse the existing backend-seed target, which already has the correct
module path, and let a seeding failure fail the setup.
The ${VAR,,} expansion requires bash 4.0+. macOS ships bash 3.2, where
it raises "bad substitution" and fails backend-test for any contributor
on that platform. Deployment targets and CI run Linux, so only local
development was affected.

Replace it with tr, which behaves identically on both versions.
@tomvothecoder

Copy link
Copy Markdown
Collaborator

Looks good to me, thanks. You can merge if it is ready.

@tomvothecoder tomvothecoder added this to the 1. FY27Q1: Beta Launch milestone Oct 7, 2026
@tomvothecoder

Copy link
Copy Markdown
Collaborator

This actually fixes backend tests for other PRs too. I'll merge.

@tomvothecoder
tomvothecoder merged commit 7227247 into E3SM-Project:main Oct 7, 2026
1 check passed
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.

2 participants