Add on demand checks for Codra dependencies

Ouverte
#157 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
38/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
docker, node.js, postgresql, typescript

Piste de recherche

Start by reading the existing setup and runtime adapter code, then find where dependency checks can be started and how shared results are represented. Implement checks for the listed dependencies while preserving the stated on-demand PostgreSQL behavior and secret handling; verify success, failure, unavailable, and database cold start or timeout cases in both runtimes. Done means the requested checks and tests work and typecheck, test, and lint pass.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement good first issue help wanted

Goal

Build the backend checks used by Codra's manual setup and dependency check. The dashboard will start these checks and display their results in a separate subissue, #158.

Checks to support

Check the dependencies Codra can verify: GitHub App configuration and access, available webhook delivery information, model provider credentials, the configured queue or worker, and PostgreSQL. If the current runtime cannot verify a dependency, return an unavailable result instead of reporting a failure.

Important database behavior

PostgreSQL checks must happen only after an operator asks for them or when a normal Codra operation needs the database. A connection attempt may wake a suspended serverless database. Do not add scheduled probes, keep alive connections, or other behavior that prevents it from suspending. If a cold start or timeout occurs, report it clearly where possible.

Implementation guidance

Keep the check result format in shared code, and use the existing runtime adapters to perform checks that depend on Cloudflare or Node/Docker services. Do not expose API keys, private keys, or other secrets in results or logs. Check the current setup and permission state without changing it.

Done when

  • Each supported dependency returns passed, failed, or unavailable with a short explanation and next step.
  • PostgreSQL is checked on demand and is not kept awake.
  • The behavior works in both Cloudflare Workers and Node/Docker. Runtime specific checks may be unavailable when a runtime lacks the needed access.
  • Tests cover success, failure, unavailable results, and database cold start or timeout behavior.
  • npm run typecheck, npm test, and npm run lint all pass.
Langage dominant
TypeScript
Étoiles
125
Forks
23
Merge moyen
2 j 13 h
PR mergées (30 j)
12

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de devarshishimpi/codra

Toutes les issues de devarshishimpi/codra

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.