azaion/detections
1
0
Fork 0
mirror of https://github.com/azaion/detections.git synced 2026-04-22 08:36:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update autopilot state and dependencies table for architecture shift

Browse Source 
- Changed the current step from "Refactor" to "Implement" in the autopilot state, indicating a transition to the next phase of development.
- Updated the dependencies table to reflect the completion of 11 tasks and the addition of 4 new tasks related to the distributed architecture.
- Removed outdated task documentation for AZ-173, AZ-174, AZ-175, and AZ-176 as they are now obsolete following the architectural changes.
- Enhanced the execution order for new tasks, organizing them into batches based on dependencies.

These updates aim to align the project documentation with the current development phase and improve clarity on task management moving forward.
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-03-31 06:08:44 +03:00
parent 8ce40a9385
commit 6547c5903a
6 changed files with 48 additions and 102 deletions
Download Patch File Download Diff File Expand all files Collapse all files
_docs/02_tasks/_dependencies_table.md
+34 -46
View File
@@ -1,56 +1,44 @@
# Dependencies Table
**Date**: 2026-03-22
**Total Tasks**: 11
**Total Complexity Points**: 35
**Date**: 2026-03-31
**Total Tasks**: 15 (11 done + 4 new)
**Total Complexity Points**: 43
| Task | Name | Complexity | Dependencies | Epic |
|------|------|-----------|-------------|------|
| AZ-138 | test_infrastructure | 5 | None | AZ-137 |
| AZ-139 | test_health_engine | 3 | AZ-138 | AZ-137 |
| AZ-140 | test_single_image | 3 | AZ-138 | AZ-137 |
| AZ-141 | test_tiling | 3 | AZ-138 | AZ-137 |
| AZ-142 | test_async_sse | 3 | AZ-138 | AZ-137 |
| AZ-143 | test_video | 3 | AZ-138, AZ-142 | AZ-137 |
| AZ-144 | test_negative | 2 | AZ-138 | AZ-137 |
| AZ-145 | test_resilience | 5 | AZ-138, AZ-142 | AZ-137 |
| AZ-146 | test_performance | 3 | AZ-138 | AZ-137 |
| AZ-147 | test_security | 2 | AZ-138 | AZ-137 |
| AZ-148 | test_resource_limits | 3 | AZ-138, AZ-142 | AZ-137 |
## Completed Tasks (Steps 4-6)
## Test Scenario Coverage
| Task | Name | Complexity | Dependencies | Epic | Status |
|------|------|-----------|-------------|------|--------|
| AZ-138 | test_infrastructure | 5 | None | AZ-137 | done |
| AZ-139 | test_health_engine | 3 | AZ-138 | AZ-137 | done |
| AZ-140 | test_single_image | 3 | AZ-138 | AZ-137 | done |
| AZ-141 | test_tiling | 3 | AZ-138 | AZ-137 | done |
| AZ-142 | test_async_sse | 3 | AZ-138 | AZ-137 | done |
| AZ-143 | test_video | 3 | AZ-138, AZ-142 | AZ-137 | done |
| AZ-144 | test_negative | 2 | AZ-138 | AZ-137 | done |
| AZ-145 | test_resilience | 5 | AZ-138, AZ-142 | AZ-137 | done |
| AZ-146 | test_performance | 3 | AZ-138 | AZ-137 | done |
| AZ-147 | test_security | 2 | AZ-138 | AZ-137 | done |
| AZ-148 | test_resource_limits | 3 | AZ-138, AZ-142 | AZ-137 | done |
| Task | Scenarios |
|------|-----------|
| AZ-138 | Infrastructure scaffold (no test scenarios) |
| AZ-139 | FT-P-01, FT-P-02, FT-P-14, FT-P-15 |
| AZ-140 | FT-P-03, FT-P-05, FT-P-06, FT-P-07, FT-P-13 |
| AZ-141 | FT-P-04, FT-P-16 |
| AZ-142 | FT-P-08, FT-P-09, FT-N-04 |
| AZ-143 | FT-P-10, FT-P-11, FT-P-12 |
| AZ-144 | FT-N-01, FT-N-02, FT-N-03, FT-N-05 |
| AZ-145 | FT-N-06, FT-N-07, NFT-RES-01, NFT-RES-02, NFT-RES-03, NFT-RES-04 |
| AZ-146 | NFT-PERF-01, NFT-PERF-02, NFT-PERF-03, NFT-PERF-04 |
| AZ-147 | NFT-SEC-01, NFT-SEC-02, NFT-SEC-03 |
| AZ-148 | FT-N-08, NFT-RES-LIM-01, NFT-RES-LIM-02, NFT-RES-LIM-03, NFT-RES-LIM-04 |
## New Tasks (Step 8 — Distributed Architecture)
**Total scenarios**: 39/39 covered
| Task | Name | Complexity | Dependencies | Epic | Status |
|------|------|-----------|-------------|------|--------|
| AZ-173 | stream_based_run_detect | 3 | None | AZ-172 | todo |
| AZ-174 | db_driven_ai_config | 2 | None | AZ-172 | todo |
| AZ-175 | media_table_integration | 2 | AZ-173 | AZ-172 | todo |
| AZ-176 | cleanup_obsolete_path_code | 1 | AZ-173, AZ-174 | AZ-172 | todo |
## Execution Order
## Execution Order (New Tasks)
**Batch 1** (no dependencies beyond infrastructure):
- AZ-138: test_infrastructure (5 pts)
**Batch 1** (no internal dependencies):
- AZ-173: stream_based_run_detect (3 pts) — PyAV byte-stream decoding
- AZ-174: db_driven_ai_config (2 pts) — fetch config from annotations service
**Batch 2** (depends on AZ-138 only):
- AZ-139: test_health_engine (3 pts)
- AZ-140: test_single_image (3 pts)
- AZ-141: test_tiling (3 pts)
- AZ-142: test_async_sse (3 pts)
- AZ-144: test_negative (2 pts)
- AZ-146: test_performance (3 pts)
- AZ-147: test_security (2 pts)
**Batch 2** (depends on AZ-173):
- AZ-175: media_table_integration (2 pts) — Media record lifecycle
**Batch 3** (depends on AZ-138 + AZ-142):
- AZ-143: test_video (3 pts)
- AZ-145: test_resilience (5 pts)
- AZ-148: test_resource_limits (3 pts)
**Batch 3** (depends on AZ-173 + AZ-174):
- AZ-176: cleanup_obsolete_path_code (1 pt) — remove old path-based code
**New tasks total**: 4 tasks, 8 complexity points, 3 batches
_docs/02_tasks/backlog/AZ-173_stream_based_run_detect.md → _docs/02_tasks/todo/AZ-173_stream_based_run_detect.md
+10 -7
View File
@@ -38,16 +38,19 @@ Remove:
- `paths` iteration loop in `run_detect`
- Direct `cv2.VideoCapture(local_path)` and `cv2.imread(local_path)` calls
## Video Stream Processing Options
## Video Stream Processing — PyAV (preferred)
**Option A: Write-then-read**
Write entire upload to temp file, then open with `cv2.VideoCapture`. Simple but not real-time.
Use **PyAV** (`av` package) for byte-stream video decoding. Preferred approach per user decision.
**Option B: Concurrent pipe**
One thread writes incoming bytes to a file; another thread reads frames via `cv2.VideoCapture` on the growing file. Requires careful synchronization.
**Why PyAV**: Decode frames directly from bytes/stream via `av.open(io.BytesIO(data))` without intermediate file I/O. Most flexible for streaming, no concurrent file read/write synchronization needed.
**Option C: PyAV byte-stream decoding**
Use `av.open(io.BytesIO(data))` or a custom `av.InputContainer` to decode frames directly from bytes without file I/O. Most flexible for streaming.
**Investigation needed during implementation**:
- Verify PyAV can decode frames from a growing `BytesIO` or chunked stream (not just complete files)
- Check if `av.open()` supports reading from an async generator or pipe for true streaming
- Evaluate whether simultaneous disk write can be done with a `tee`-style approach (write bytes to file while feeding to PyAV)
- Confirm PyAV frame format (RGB/BGR/YUV) compatibility with existing `process_frames` pipeline (expects BGR numpy arrays)
- Check PyAV version compatibility with the project's Python/Cython setup
- Fallback: if PyAV streaming is not viable, use write-then-read with `cv2.VideoCapture` on completed file
## Acceptance Criteria
_docs/02_tasks/backlog/AZ-174_db_driven_ai_config.md → _docs/02_tasks/todo/AZ-174_db_driven_ai_config.md
View File
_docs/02_tasks/backlog/AZ-175_media_table_integration.md → _docs/02_tasks/todo/AZ-175_media_table_integration.md
View File
_docs/02_tasks/backlog/AZ-176_cleanup_obsolete_path_code.md → _docs/02_tasks/todo/AZ-176_cleanup_obsolete_path_code.md
View File