fix(monitor): keep supervision after empty scans
This commit is contained in:
1 parent
c19c4ffbd9
commit
b2a41270a9
8 files changed
+90
-22
No files matched your search
+2
-2
@@ -4,8 +4,8 @@
|
||||
|
||||
## Готово
|
||||
|
||||
- **2026-10-10 update:** switched the new target password to Compose environment input (`SS_PASSWORD`), removed `DAC_OVERRIDE` and secret-file mount, and clear the variable before launching child processes. Commit: `558b215`; local `go test ./...`, build, Compose config, static deploy guard and entrypoint syntax passed. Remote read-only checks found Docker 29.8.2, the old target still running untouched, and host SOCKS port 11080 free. No target/state was created. Remote deployment is currently blocked because SSH MCP `sftp-upload-file` has no configured `defaults.transferRoot`; direct SCP is unavailable. Configure its transfer root as `/tmp/opencode` (or provide another upload path) to continue the full fresh-target acceptance.
|
||||
- Added `managed monitor` and supervision only in the dedicated target entrypoint: guarded target-owned DB/identity before singleton, policy 5m/3/30m with bounded CLI/env validation, owned-loopback Player API probe/discovery without direct fallback, fixed blockcheck/zapret argv with context cancellation/join. Startup bootstraps only without a qualified active frontend, tries saved scenarios first, then scans; unresolved GGC keeps monitoring; safety/DB errors stop it. SIGTERM waits for monitor restoration before stopping target-local zapret/SS. Local fake CLI/entrypoint tests are present. Live remote behavior remains unverified; the existing target and Xray are unchanged.
|
||||
- **2026-10-10 remote acceptance:** target image built from pinned base and started in a fresh directory/state volume; host SOCKS port `11080` was free, old container stayed untouched. Initial managed status confirmed generation `0`, `groups=none`, no active candidate IDs, and `NFQWS2_ENABLE=0`. Automated frontend scan of `youtube.com` completed with `total=4323, working=0`; candidate check produced an empty `strategies` array, recorded one failed run, and bootstrap error caused monitor/entrypoint exit. No strategy was applied. New target remains stopped with its fresh, strategy-free state preserved. This exposed that managed bootstrap should scan the actual Player API host (`www.youtube.com`) and ordinary no-candidate errors must not terminate ongoing monitoring. Updated code/tests are in progress; rerun required. Old container and Xray were not changed.
|
||||
- Added `managed monitor` and supervision only in the dedicated target entrypoint: guarded target-owned DB/identity before singleton, policy 5m/3/30m with bounded CLI/env validation, owned-loopback Player API probe/discovery without direct fallback, fixed blockcheck/zapret argv with context cancellation/join. Startup bootstraps only without a qualified active frontend, tries saved scenarios first, then scans; unresolved GGC keeps monitoring; safety/DB errors stop it. SIGTERM waits for monitor restoration before stopping target-local zapret/SS. Local fake CLI/entrypoint tests are present.
|
||||
|
||||
- Hardened managed recovery artifacts: общий `revalidateCandidate` удаляет старый combined JSON перед каждым check, remove errors/missing/malformed report fail closed; scan shortlist проверяется на regular file и mtime не раньше whole-second scan start (production использует unique temp path). Добавлены fake-only regression tests stale/missing shortlist, stale combined, remove failure и infrastructure classification/restoration. Tests/build/network не запускались; verification deferred orchestrator, CLI/entrypoint не добавлены.
|
||||
|
||||
|
||||
Reference in new issue
Block a user