adam/open-swe
1
0
Fork 0
mirror of https://github.com/Sea-Haven-Industries/open-swe.git synced 2026-09-30 08:03:15 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
open-swe/deploy
History
Adam Moussa f2633f9bd0
Some checks are pending
Build & publish app artifacts / Publish + deploy (dev) (push) Waiting to run
Details
Build & publish app artifacts / Publish + deploy (prod) (push) Waiting to run
Details
Infra CD / Infra CI (pre-deploy) (push) Waiting to run
Details
Infra CD / Deploy open-swe-dev (push) Blocked by required conditions
Details
Infra CD / Deploy open-swe-prod (push) Blocked by required conditions
Details
fix: don't crash-loop the box when no user mapping is configured (#25) 
seed_store.sh (ExecStartPost) exited 1 when it couldn't resolve a user_mappings
entry, which — with Type=simple — fails the whole unit and crash-loops the box. This
contradicts the script's own OSWE-SEED-03 precedent (the server-not-ready path exits
0 specifically to avoid a restart loop). A missing user mapping is a seeding gap, not
an unhealthy server: the @openswe trigger just won't resolve a commenter, which a
deployment-validation env (dev) does not need.

Make it non-fatal — warn and skip the user_mappings seed; team_settings is still
seeded and the service starts. The empty MAPPINGS array makes the seed loop a no-op.
Set SEED_USER_MAPPINGS / CONFIGURED_ADMINS / OPENSWE_OWNER_LOGIN+EMAIL to seed it.

Verified on the dev box: service active, langgraph bound to 127.0.0.1:2024 (loopback),
/ok 200, /healthz 200.
2026-06-26 20:06:53 -04:00
..
ami fix(deploy): use %%...%% for CDK user-data tokens (don't collide with @@ sed) (#21) 2026-06-26 19:06:37 -04:00
seahaven fix: don't crash-loop the box when no user mapping is configured (#25) 2026-06-26 20:06:53 -04:00