[Bug]: Vector-index health reports `index-reindex-hourly scheduled` (OK) when no cron entry is installed
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 72/100
Línea de trabajo
Start with check_cron in lib/vector_index_health.py:385-415 and the cron installation warning in bin/fw:4472; trace how fw cron install records whether the registry was deployed and where FW_CRON_INSTALL_DIR points. Reproduce with an active registry entry and no installed cron job, then run fw doctor. Done when the health check reports OK only for a deployed job and otherwise explains that installation is needed.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Bug Description
lib/vector_index_health.py:385-415 (check_cron) reads .context/cron-registry.yaml only. If the job index-reindex-hourly is listed with status active, it returns OK cron: index-reindex-hourly scheduled. It never checks that the registry was generated and deployed (fw cron install, /etc/cron.d by default, FW_CRON_INSTALL_DIR).
In the same fw doctor run, bin/fw:4472 prints WARN Cron registry present but not generated — run: fw cron install. The two lines contradict each other, and the OK one sits inside the vector-index block, where a reader looks to learn whether the index will be refreshed.
Steps to Reproduce
- Project created by
fw init, upgraded to 1.8.11;fw cron installnever run (it needs root). ls /etc/cron.d | grep agenticreturns nothing; the user crontab has no framework entry.fw doctorprints bothOK cron: index-reindex-hourly scheduledandWARN Cron registry present but not generated — run: fw cron install.
Expected Behavior
check_cron reports what will actually run: OK only when the job is deployed; otherwise WARN or FAIL such as index-reindex-hourly declared in the registry but not installed (fw cron install).
Actual Behavior
OK cron: index-reindex-hourly scheduled while nothing is scheduled.
fw doctor output
AI Agent
Claude Code
Operating System
Linux
Additional Context
1.8.11 (e42aa41bf), vendored consumer, Linux (Ubuntu 20.04, systemd 245), Claude Code.
- Lenguaje dominante
- Shell
- Estrellas
- 16
- Forks
- 6
- Merge medio
- 6 h 24 min
- PR fusionados (30 d)
- 5
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de DimitriGeelen/agentic-engineering-framework
-
area:doctor bug severity:low status:accepted triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
DimitriGeelen/agentic-engineering-framework#100 · 3 comentarios ·
-
area:doctor bug severity:medium status:accepted triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
DimitriGeelen/agentic-engineering-framework#97 · 3 comentarios ·
-
area:context bug severity:low status:accepted triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
DimitriGeelen/agentic-engineering-framework#96 · 3 comentarios ·
-
area:cli bug severity:medium status:accepted triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
DimitriGeelen/agentic-engineering-framework#95 · 3 comentarios ·
-
area:watchtower bug severity:low status:released triaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
DimitriGeelen/agentic-engineering-framework#94 · 4 comentarios ·
Todos los issues de DimitriGeelen/agentic-engineering-framework
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
package-update
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
canUseTool drops decision_reason_type and classifier_approvable from the can_use_tool requestAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
jangala-dev/devicecode-lua#344 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
cov-lineages/pangolin#583 · 1 comentario ·