Commit 737cf44
Team Coding Agent 1
fix: persist watchdog_enabled setting from runtime_settings.json
The watchdog_enabled setting was not being applied from the
runtime_settings.json file because the code was checking if
WatchDogIdle or WatchDogBusy were set via env vars, but not
checking if WatchDog itself was set via env vars.
This caused the setting to be ignored when the user enabled
watchdog through the UI because:
1. The file was written correctly with watchdog_enabled=true
2. But on reload, the code checked !envWatchdogIdle && !envWatchdogBusy
3. This condition didn't account for the main WatchDog flag
4. So the setting from file was never applied
Fix:
- Add envWatchdog check to track if WatchDog was set via env var
- Apply WatchdogEnabled from file when not set via env
- Also disable WatchDogIdle and WatchDogBusy when watchdog is disabled
Fixes #91251 parent d3f629f commit 737cf44
1 file changed
+7
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
197 | 197 | | |
198 | 198 | | |
199 | 199 | | |
| 200 | + | |
200 | 201 | | |
201 | 202 | | |
202 | 203 | | |
| |||
352 | 353 | | |
353 | 354 | | |
354 | 355 | | |
355 | | - | |
356 | | - | |
357 | | - | |
358 | | - | |
| 356 | + | |
| 357 | + | |
| 358 | + | |
| 359 | + | |
| 360 | + | |
| 361 | + | |
359 | 362 | | |
360 | 363 | | |
361 | 364 | | |
| |||
0 commit comments