Commit e58f2a6
Baudbot
fix: unset PKG_EXECPATH and stale broker token vars in startup-cleanup
When startup-cleanup.sh runs mid-session (called by the control agent),
two inherited env vars cause bridge startup failures:
1. PKG_EXECPATH — leaked from the parent varlock-launched process, causes
varlock's SEA binary to misinterpret subcommands as Node module paths.
The varlock broker-key probes (lines 115-122) silently fail, resulting
in 'No Slack transport configured' and the bridge never starting.
2. SLACK_BROKER_ACCESS_TOKEN / SLACK_BROKER_ACCESS_TOKEN_EXPIRES_AT —
varlock does not override env vars already present in the parent
process. If the broker token was rotated after session start, the
supervisor passes the stale (expired) values instead of reading
fresh ones from ~/.config/.env.
Fix: unset PKG_EXECPATH at script top (before varlock probes), and
unset broker token vars in the supervisor subshell (before varlock run).
Regression from #148.1 parent 94790e3 commit e58f2a6
1 file changed
Lines changed: 10 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
14 | 19 | | |
15 | 20 | | |
16 | 21 | | |
| |||
140 | 145 | | |
141 | 146 | | |
142 | 147 | | |
| 148 | + | |
| 149 | + | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
143 | 153 | | |
144 | 154 | | |
145 | 155 | | |
| |||
0 commit comments