Three medium vision-manager findings: 1. **`vision_running()` conflated "container absent" with "inspect failed".** A transient docker-socket-proxy hiccup made the manager think vision had stopped, which reset `up_for`/`idle_for` and defeated MAX_UPTIME. Distinguishes: exit 0 → echo true/false; "No such container" → false; else → ERR (loop skips tick). 2. **`crawl_running()` fail-closed where `analysis_enabled()` fail-opens.** A psql `ERR` logged a misleading "RAM mutex" line every tick. Numeric-guard at the call site with a distinct log. 3. **`start_vision` left wedged containers running** on `START_HEALTH_TIMEOUT` expiry — pinned forever in not-ready state. Now `stop_vision` so next tick retries from a clean state. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
33 lines
862 B
JSON
33 lines
862 B
JSON
{
|
|
"name": "mangalord-frontend",
|
|
"version": "0.87.8",
|
|
"private": true,
|
|
"type": "module",
|
|
"scripts": {
|
|
"dev": "vite dev",
|
|
"build": "vite build",
|
|
"preview": "vite preview",
|
|
"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
|
|
"test": "vitest run",
|
|
"test:watch": "vitest",
|
|
"test:e2e": "playwright test"
|
|
},
|
|
"devDependencies": {
|
|
"@lucide/svelte": "^1.16.0",
|
|
"@playwright/test": "^1.48.0",
|
|
"@sveltejs/adapter-node": "^5.2.0",
|
|
"@sveltejs/kit": "^2.7.0",
|
|
"@sveltejs/vite-plugin-svelte": "^4.0.0",
|
|
"@testing-library/jest-dom": "^6.6.0",
|
|
"@testing-library/svelte": "^5.2.0",
|
|
"@types/node": "^22.7.0",
|
|
"jsdom": "^25.0.0",
|
|
"svelte": "^5.0.0",
|
|
"svelte-check": "^4.0.0",
|
|
"tslib": "^2.7.0",
|
|
"typescript": "^5.6.0",
|
|
"vite": "^5.4.0",
|
|
"vitest": "^2.1.0"
|
|
}
|
|
}
|