Feature/issue 10 alert delivery worker#57
Conversation
… flag, add config health validation - Add cv_dev development key bypass for local testing - Require X-API-Key on all mutation endpoints (POST predict, orgs, alerts, subscriptions) - Surface is_synthetic at root of inference response for frontend demo banners - Expand /api/health to validate config alignment (bands vs in_channels, classes vs num_classes)
- Add FastAPI test client fixture - Create CI workflow for Python (flake8, pytest) and frontend (npm build) - Bootstrap tests/ directory structure
- Parametrize UNet init for all 3 analysis types (4ch/2cl, 4ch/3cl, 3ch/3cl) - Validate forward pass output shapes - Add Siamese change detection forward shape test
- Link to 6 active good-first-issue and help-wanted issues - Add claim workflow for new contributors - Include time estimates and skill-building map
- ../components/map/ -> ../components/Map/ - Fixes vite build failure on Linux (case-sensitive filesystem)
- Fixes pip install failure for gdal and rasterio on Ubuntu runners - Adds libgdal-dev, gdal-bin, libgl1-mesa-glx
- gdal Python package requires exact system GDAL version matching - rasterio covers all GDAL functionality we actually use - Simplify CI system deps to libgl1 only (for opencv runtime)
- Fixes ModuleNotFoundError: No module named 'climatevision' - pip install -e . registers src/ as an importable package
- ForestDataset with DataLoader support - Training/validation augmentation pipelines - Synthetic tile generation for demo/fallback mode
- Add DONE/PENDING task list for April 2026 sprint - Include actual .github/workflows/ci.yml code in role doc - Update local CI check commands to match current workflow
|
Thank you @Presmanes3 this is solid work and the commit table in the description is a nice touch. Unfortunately we received another implementation of the same feature (#62) that targets Your contribution here especially the retry logic and the structured commit breakdown genuinely helped shape what the final implementation needed to cover. Please don't be discouraged; the work was good and I'd encourage you to pick up another open issue. |
Hi @Oshgig No problem! Thank you for the feedback. Could you please review #58 #59 #60 #61 ? I think the proyect is quite monolithic and will have some problems in the long term. I would love to keep contributing and would like to know if you are open to some refactoring... Thank you! |
5 participants
Summary
GET /api/organizations/{org_id}/alerts/pendingfor monitoringCommits
749230489d61b2d70356d69757a7bab0cbbCloses #10