fix(occupancy): address review follow-ups from PR #53 and #54 (#65, #66) #117

Merged

gabogg merged 3 commits from fix/occupancy-review-followups-53-54 into master 2026-09-25 19:22:59 +00:00

Conversation 2 Commits 3 Files changed 9 +405 -102

gabogg commented 2026-09-25 18:49:04 +00:00

Owner

Copy link

Problem Statement

This PR resolves non-blocking follow-up findings from the reviews of PR #53 (#65) and PR #54 (#66):

• #65 (PR #53 review follow-ups):
  1. Unlisted group flag was not retried after a failed write because in-memory skip reasons were cached before DB write.
  2. Stale is_unlisted=True state persisted indefinitely when a group disappeared from Artemis count_list and group_list.
  3. Startup coupling in lifespan: an exception in enforce_counting_integrity_async skipped initial count sync and anomaly reconciliation.
  4. Untyped dictionary returned by OccupancyRepository.get_camera_async and raw dictionary cam_payload.
  5. In-memory _group_skip_reasons state drifted from DB when groups disappeared or became listed.
  6. Data clump group_cam_map stored raw dicts instead of a typed structure.
  7. Type placement: GroupMember and GroupSkipReason lived in the service with sentence values rather than standard codes in schema.
  8. QuarantineTally.total ambiguously named; should be passages.
  9. Inconsistent Starlette 422 constants (HTTP_422_UNPROCESSABLE_ENTITY vs HTTP_422_UNPROCESSABLE_CONTENT).
• #66 (PR #54 review follow-ups):
  1. Third copy of the counted-camera rule: comment claimed all published figures read through SQL filter, but ranking lists re-applied not is_excluded and is_active in Python.
  2. Window-end mismatch: get_hourly_flow_distribution_async ended at <= cycle_end, while get_bucketed_cycle_flow_async used < ?.
  3. Test helper _insert_event in test_trust_dataset_parity.py took ambiguous hour and overriding at arguments.
  4. Glossary wording in CONTEXT.md for Multi-camera group contradicted invariant definition ("does not allow for" vs "does not account for").
  5. Parity boundary test used an edge (+ 24*3600) that real callers never pass, creating a 25th bucket (hour_idx = 24).

Architectural Approach

1. Unlisted Group & Skip Reason Lifecycle (#65 items 1, 2, 5):
   • In OccupancyManager._skip_group_async: persist is_unlisted via repo.mark_group_unlisted_async before caching the reason in self._group_skip_reasons.
   • In OccupancyRepository: make mark_group_unlisted_async idempotent, and add clear_stale_unlisted_groups_async to clear is_unlisted=0 for groups no longer reported.
   • At the start of each passenger flow poll, prune self._group_skip_reasons for codes not in count_list, and pop registered groups on camera group registration.
2. Startup Decoupling (#65 item 3):
   • In app/main.py: lifespan, isolate enforce_counting_integrity_async in its own try/except block.
3. Typing & Schema Cleanups (#65 items 4, 6, 7, 8, 9):
   • Move GroupMember, GroupSkipReason (with short enum values and GROUP_SKIP_MESSAGES), and GroupDirectionMapping into app/schemas/occupancy_models.py.
   • Add resource_group_code to CountingCameraItem; make get_camera_async return CountingCameraItem | None and upsert_camera_async handle both schema and dict.
   • Rename QuarantineTally.total to passages with a docstring and backwards-compatible property/validator.
   • Unify on status.HTTP_422_UNPROCESSABLE_CONTENT in app/main.py and pin starlette>=0.37.2 in requirements.txt.
4. Window Conventions & Counted-Camera Rule (#66 items 1, 2, 3, 4, 5):
   • Clarify _COUNTED_CAMERA_JOIN / _COUNTED_CAMERA_FILTER comment and use _is_counted_camera helper for top entrance/exit ranking.
   • Change get_bucketed_cycle_flow_async to use inclusive <= ?, and update analytics_service.py to pass bounds.end.
   • Update CONTEXT.md glossary wording to "does not account for".
   • Refactor tests/test_trust_dataset_parity.py: use CYCLE_END = CYCLE_START + 24*3600 - 0.001, helper _hour_epoch(hour), and assert bucket indices 0 and 23.
5. Regression Tests:
   • Added tests in tests/test_counting_integrity.py verifying unlisted write retry, stale unlisted state cleanup, and decoupled startup integrity checks.

Verification Evidence

• ruff check .: Passed cleanly with zero warnings/errors.
• ruff format --check .: Passed, all 129 files formatted.
• git diff --check: Passed, zero trailing whitespace or formatting defects.
• node --test: 80 passed in 1.0s.
• pytest -q -o faulthandler_timeout=30: 336 passed, 0 failed, 1 skipped in 66s.
• Pre-commit hook: All hooks passed cleanly.

Closes #65
Closes #66

## Problem Statement This PR resolves non-blocking follow-up findings from the reviews of PR #53 (#65) and PR #54 (#66): - **#65 (PR #53 review follow-ups)**: 1. Unlisted group flag was not retried after a failed write because in-memory skip reasons were cached before DB write. 2. Stale `is_unlisted=True` state persisted indefinitely when a group disappeared from Artemis `count_list` and `group_list`. 3. Startup coupling in `lifespan`: an exception in `enforce_counting_integrity_async` skipped initial count sync and anomaly reconciliation. 4. Untyped dictionary returned by `OccupancyRepository.get_camera_async` and raw dictionary `cam_payload`. 5. In-memory `_group_skip_reasons` state drifted from DB when groups disappeared or became listed. 6. Data clump `group_cam_map` stored raw dicts instead of a typed structure. 7. Type placement: `GroupMember` and `GroupSkipReason` lived in the service with sentence values rather than standard codes in schema. 8. `QuarantineTally.total` ambiguously named; should be `passages`. 9. Inconsistent Starlette 422 constants (`HTTP_422_UNPROCESSABLE_ENTITY` vs `HTTP_422_UNPROCESSABLE_CONTENT`). - **#66 (PR #54 review follow-ups)**: 1. Third copy of the counted-camera rule: comment claimed all published figures read through SQL filter, but ranking lists re-applied `not is_excluded and is_active` in Python. 2. Window-end mismatch: `get_hourly_flow_distribution_async` ended at `<= cycle_end`, while `get_bucketed_cycle_flow_async` used `< ?`. 3. Test helper `_insert_event` in `test_trust_dataset_parity.py` took ambiguous `hour` and overriding `at` arguments. 4. Glossary wording in `CONTEXT.md` for Multi-camera group contradicted invariant definition ("does not allow for" vs "does not account for"). 5. Parity boundary test used an edge (`+ 24*3600`) that real callers never pass, creating a 25th bucket (`hour_idx = 24`). ## Architectural Approach 1. **Unlisted Group & Skip Reason Lifecycle (#65 items 1, 2, 5)**: - In `OccupancyManager._skip_group_async`: persist `is_unlisted` via `repo.mark_group_unlisted_async` *before* caching the reason in `self._group_skip_reasons`. - In `OccupancyRepository`: make `mark_group_unlisted_async` idempotent, and add `clear_stale_unlisted_groups_async` to clear `is_unlisted=0` for groups no longer reported. - At the start of each passenger flow poll, prune `self._group_skip_reasons` for codes not in `count_list`, and pop registered groups on camera group registration. 2. **Startup Decoupling (#65 item 3)**: - In `app/main.py: lifespan`, isolate `enforce_counting_integrity_async` in its own `try/except` block. 3. **Typing & Schema Cleanups (#65 items 4, 6, 7, 8, 9)**: - Move `GroupMember`, `GroupSkipReason` (with short enum values and `GROUP_SKIP_MESSAGES`), and `GroupDirectionMapping` into `app/schemas/occupancy_models.py`. - Add `resource_group_code` to `CountingCameraItem`; make `get_camera_async` return `CountingCameraItem | None` and `upsert_camera_async` handle both schema and dict. - Rename `QuarantineTally.total` to `passages` with a docstring and backwards-compatible property/validator. - Unify on `status.HTTP_422_UNPROCESSABLE_CONTENT` in `app/main.py` and pin `starlette>=0.37.2` in `requirements.txt`. 4. **Window Conventions & Counted-Camera Rule (#66 items 1, 2, 3, 4, 5)**: - Clarify `_COUNTED_CAMERA_JOIN` / `_COUNTED_CAMERA_FILTER` comment and use `_is_counted_camera` helper for top entrance/exit ranking. - Change `get_bucketed_cycle_flow_async` to use inclusive `<= ?`, and update `analytics_service.py` to pass `bounds.end`. - Update `CONTEXT.md` glossary wording to "does not account for". - Refactor `tests/test_trust_dataset_parity.py`: use `CYCLE_END = CYCLE_START + 24*3600 - 0.001`, helper `_hour_epoch(hour)`, and assert bucket indices 0 and 23. 5. **Regression Tests**: - Added tests in `tests/test_counting_integrity.py` verifying unlisted write retry, stale unlisted state cleanup, and decoupled startup integrity checks. ## Verification Evidence - `ruff check .`: Passed cleanly with zero warnings/errors. - `ruff format --check .`: Passed, all 129 files formatted. - `git diff --check`: Passed, zero trailing whitespace or formatting defects. - `node --test`: 80 passed in 1.0s. - `pytest -q -o faulthandler_timeout=30`: 336 passed, 0 failed, 1 skipped in 66s. - Pre-commit hook: All hooks passed cleanly. Closes #65 Closes #66

gabogg added 1 commit 2026-09-25 18:49:05 +00:00

fix(occupancy): address review follow-ups from PR #53 and #54 (#65, #66) ... 07741149a3

- Fix unlisted group retry on write failure and clear stale unlisted state when groups disappear (#65 items 1, 2, 5)
- Decouple counting integrity check in startup lifespan so exceptions do not abort counts sync (#65 item 3)
- Use typed CountingCameraItem schema in repository get_camera_async and camera sync (#65 item 4)
- Introduce GroupDirectionMapping structure for group camera routing (#65 item 6)
- Consolidate group types in app/schemas/occupancy_models.py with short skip codes and message mapping (#65 item 7)
- Rename QuarantineTally.total to passages with backwards-compatible property and docstring (#65 item 8)
- Update Starlette status codes to HTTP_422_UNPROCESSABLE_CONTENT and pin starlette>=0.37.2 (#65 item 9)
- Clarify counted-camera rule comments in repository and use _is_counted_camera helper for rankings (#66 item 1)
- Align get_bucketed_cycle_flow_async with repository convention using inclusive cycle window end <= ? (#66 item 2)
- Clean up parity test timestamp helper with _hour_epoch and single epoch parameter (#66 item 3)
- Clarify multi-camera group glossary wording in CONTEXT.md (#66 item 4)
- Test boundary events with production -0.001 cycle end and assert bucket indices 0 and 23 (#66 item 5)

gabogg commented 2026-09-25 19:03:35 +00:00

Author

Owner

Copy link

Two-Axis Code Review (PR #117)

Standards

1. Documented Standard Violations (Hard Violations)

• OccupancyRepository.upsert_camera_async (app/db/occupancy_repository.py):

  • Standard: docs/standards/code-standards.md §2.3 (Pydantic Schemas: "Avoid passing untyped, raw dictionaries between service layers when structured schemas are available").
  • Violation: The method accepts CountingCameraItem | dict[str, Any] and returns untyped dict[str, Any]. In app/services/occupancy_service.py:477, callers also pass raw dict {"camera_index_code": ec_code, "is_active": False}, bypassing strict model validation.

• GroupMember and GroupDirectionMapping (app/schemas/occupancy_models.py):

  • Standard: docs/standards/code-standards.md §2.3 ("Use Pydantic v2 schemas in app/schemas/ for all API request bodies and structured data payloads") and AGENTS.md §2.
  • Violation: Both structures are defined as typing.NamedTuple rather than Pydantic v2 BaseModel classes, breaking schema modeling consistency in app/schemas/.

2. Baseline Smells (Judgement Calls)

• Feature Envy & Primitive Obsession — app/db/occupancy_repository.py:

  def _is_counted_camera(camera: dict[str, Any]) -> bool:
      """Check if a camera dictionary represents a counted camera (active and not excluded)."""
      return bool(camera.get("is_active")) and not bool(camera.get("is_excluded"))
  

  Assessment: The helper envies camera attributes via untyped dictionary lookups (dict[str, Any]). This predicate belongs as an is_counted property directly on CountingCameraItem.

• Primitive Obsession — OccupancyRepository.upsert_camera_async (app/db/occupancy_repository.py):

  if isinstance(cam, BaseModel):
      cam_dict = cam.model_dump()
  else:
      cam_dict = cam
  

  Assessment: Degrades typed Pydantic models back into raw dict[str, Any] and returns a dictionary instead of maintaining CountingCameraItem.

• Primitive Obsession — tests/test_trust_dataset_parity.py:

  CYCLE_END = CYCLE_START + 24 * 3600 - 0.001
  

  Assessment: Hardcodes the magic float 0.001 instead of referencing the domain constant CYCLE_END_EPSILON from app.facility_time.

---

Spec

(a) Missing or Partial Requirements

• Issue #66, Item 2:

  "Window-end mismatch. get_hourly_flow_distribution_async ends at <= cycle_end, while get_bucketed_cycle_flow_async used < ?. Decide one convention for cycle windows."

  Finding: Partial caller migration. While OccupancyRepository.get_bucketed_cycle_flow_async was updated from < ? to <= ? and AnalyticsService.get_business_cycle_breakdown_async was switched to pass bounds.end, AnalyticsService.get_cycle_timeseries_async was omitted and still passes end_epoch = cycle.next_start.

(b) Behaviour in Diff Not Asked For (Scope Creep)

• Issue #65, Item 3:

  "Startup coupling — In app/main.py, if enforce_counting_integrity_async raises, sync_initial_counts_from_artemis_async and reconcile_and_quarantine_historical_anomalies_async skipped. Fix: give integrity check its own try."

  Finding: In app/main.py, occupancy_manager.sync_cameras_from_artemis_async() was also wrapped in its own dedicated try/except block. The spec only asked to decouple enforce_counting_integrity_async so counts sync and anomaly reconciliation wouldn't abort if integrity enforcement failed.

(c) Requirements Implemented Where Implementation Looks Wrong

• Issue #66, Item 2:

  "Window-end mismatch. get_hourly_flow_distribution_async ends at <= cycle_end, while get_bucketed_cycle_flow_async used < ?. Decide one convention for cycle windows."

  Finding: Because OccupancyRepository.get_bucketed_cycle_flow_async now evaluates timestamp_epoch <= ?, the un-migrated caller AnalyticsService.get_cycle_timeseries_async queries the closed interval [cycle.start, cycle.next_start]. An event stamped exactly at cycle.next_start (which belongs to the subsequent cycle) matches in SQL with bucket_idx = 24. Although get_cycle_timeseries_async silently discards it via 0 <= idx < num_buckets, the query improperly spans across cycle boundaries.

---

Summary: 5 findings in Standards (worst: upsert_camera_async accepting and returning untyped dictionaries in violation of §2.3); 3 findings in Spec (worst: un-migrated caller AnalyticsService.get_cycle_timeseries_async matching across cycle boundaries under the new inclusive <= ? window convention).

## Two-Axis Code Review (PR #117) ### Standards #### 1. Documented Standard Violations (Hard Violations) - **`OccupancyRepository.upsert_camera_async` (`app/db/occupancy_repository.py`)**: - **Standard**: `docs/standards/code-standards.md` §2.3 (*Pydantic Schemas: "Avoid passing untyped, raw dictionaries between service layers when structured schemas are available"*). - **Violation**: The method accepts `CountingCameraItem | dict[str, Any]` and returns untyped `dict[str, Any]`. In `app/services/occupancy_service.py:477`, callers also pass raw dict `{"camera_index_code": ec_code, "is_active": False}`, bypassing strict model validation. - **`GroupMember` and `GroupDirectionMapping` (`app/schemas/occupancy_models.py`)**: - **Standard**: `docs/standards/code-standards.md` §2.3 (*"Use Pydantic v2 schemas in app/schemas/ for all API request bodies and structured data payloads"*) and `AGENTS.md` §2. - **Violation**: Both structures are defined as `typing.NamedTuple` rather than Pydantic v2 `BaseModel` classes, breaking schema modeling consistency in `app/schemas/`. #### 2. Baseline Smells (Judgement Calls) - **Feature Envy & Primitive Obsession** — `app/db/occupancy_repository.py`: ```python def _is_counted_camera(camera: dict[str, Any]) -> bool: """Check if a camera dictionary represents a counted camera (active and not excluded).""" return bool(camera.get("is_active")) and not bool(camera.get("is_excluded")) ``` *Assessment*: The helper envies camera attributes via untyped dictionary lookups (`dict[str, Any]`). This predicate belongs as an `is_counted` property directly on `CountingCameraItem`. - **Primitive Obsession** — `OccupancyRepository.upsert_camera_async` (`app/db/occupancy_repository.py`): ```python if isinstance(cam, BaseModel): cam_dict = cam.model_dump() else: cam_dict = cam ``` *Assessment*: Degrades typed Pydantic models back into raw `dict[str, Any]` and returns a dictionary instead of maintaining `CountingCameraItem`. - **Primitive Obsession** — `tests/test_trust_dataset_parity.py`: ```python CYCLE_END = CYCLE_START + 24 * 3600 - 0.001 ``` *Assessment*: Hardcodes the magic float `0.001` instead of referencing the domain constant `CYCLE_END_EPSILON` from `app.facility_time`. --- ### Spec #### (a) Missing or Partial Requirements - **Issue #66, Item 2**: > *"Window-end mismatch. get_hourly_flow_distribution_async ends at <= cycle_end, while get_bucketed_cycle_flow_async used < ?. Decide one convention for cycle windows."* **Finding**: Partial caller migration. While `OccupancyRepository.get_bucketed_cycle_flow_async` was updated from `< ?` to `<= ?` and `AnalyticsService.get_business_cycle_breakdown_async` was switched to pass `bounds.end`, `AnalyticsService.get_cycle_timeseries_async` was omitted and still passes `end_epoch = cycle.next_start`. #### (b) Behaviour in Diff Not Asked For (Scope Creep) - **Issue #65, Item 3**: > *"Startup coupling — In app/main.py, if enforce_counting_integrity_async raises, sync_initial_counts_from_artemis_async and reconcile_and_quarantine_historical_anomalies_async skipped. Fix: give integrity check its own try."* **Finding**: In `app/main.py`, `occupancy_manager.sync_cameras_from_artemis_async()` was also wrapped in its own dedicated `try/except` block. The spec only asked to decouple `enforce_counting_integrity_async` so counts sync and anomaly reconciliation wouldn't abort if integrity enforcement failed. #### (c) Requirements Implemented Where Implementation Looks Wrong - **Issue #66, Item 2**: > *"Window-end mismatch. get_hourly_flow_distribution_async ends at <= cycle_end, while get_bucketed_cycle_flow_async used < ?. Decide one convention for cycle windows."* **Finding**: Because `OccupancyRepository.get_bucketed_cycle_flow_async` now evaluates `timestamp_epoch <= ?`, the un-migrated caller `AnalyticsService.get_cycle_timeseries_async` queries the closed interval `[cycle.start, cycle.next_start]`. An event stamped exactly at `cycle.next_start` (which belongs to the subsequent cycle) matches in SQL with `bucket_idx = 24`. Although `get_cycle_timeseries_async` silently discards it via `0 <= idx < num_buckets`, the query improperly spans across cycle boundaries. --- **Summary**: 5 findings in **Standards** (worst: `upsert_camera_async` accepting and returning untyped dictionaries in violation of §2.3); 3 findings in **Spec** (worst: un-migrated caller `AnalyticsService.get_cycle_timeseries_async` matching across cycle boundaries under the new inclusive `<= ?` window convention).

gabogg added 1 commit 2026-09-25 19:17:18 +00:00

fix(occupancy): address review findings on typing, camera models, and timeseries window ... 203696d61f

- Define GroupMember and GroupDirectionMapping as Pydantic BaseModels (code-standards §2.3)
- Add is_counted property to CountingCameraItem and update _is_counted_camera to use it
- Return CountingCameraItem from OccupancyRepository.upsert_camera_async and use typed model in obsolete camera deactivation
- Query [cycle.start, cycle.end] in AnalyticsService.get_cycle_timeseries_async to prevent cross-cycle matching under inclusive window convention
- Use CYCLE_END_EPSILON in test_trust_dataset_parity.py and verify bucketed edge exclusion

gabogg commented 2026-09-25 19:17:24 +00:00

Author

Owner

Copy link

Addressed Review Findings (Commit 203696d)

All findings identified in the two-axis code review have been addressed:

1. Standards — Pydantic Schemas & Typing:

   • Converted GroupMember and GroupDirectionMapping from NamedTuple to Pydantic v2 BaseModel classes in app/schemas/occupancy_models.py.
   • Updated OccupancyRepository.upsert_camera_async signature and return value to return CountingCameraItem.
   • Replaced raw dictionary payloads with CountingCameraItem instances when deactivating obsolete cameras in OccupancyManager.sync_cameras_from_artemis_async.

2. Standards — Smells & Domain Consistency:

   • Added is_counted property directly on CountingCameraItem and updated _is_counted_camera to delegate to it.
   • Replaced magic float 0.001 in tests/test_trust_dataset_parity.py with domain constant CYCLE_END_EPSILON from app.facility_time.

3. Spec — Window-End Convention Parity:

   • Aligned AnalyticsService.get_cycle_timeseries_async to query [cycle.start, cycle.end] using the inclusive <= ? convention while sizing bucket arrays using cycle.next_start, preventing boundary event leakage into the 25th bucket.
   • Enhanced test_window_bounds_match_at_the_cycle_edges in tests/test_trust_dataset_parity.py to verify that both get_hourly_flow_distribution_async and get_bucketed_cycle_flow_async match identical bucket distributions and exclude events at cycle.next_start.

All checks, linters (ruff), and full test suites (pytest 336 passed, node --test 80 passed) are green.

### Addressed Review Findings (Commit `203696d`) All findings identified in the two-axis code review have been addressed: 1. **Standards — Pydantic Schemas & Typing**: - Converted `GroupMember` and `GroupDirectionMapping` from `NamedTuple` to Pydantic v2 `BaseModel` classes in `app/schemas/occupancy_models.py`. - Updated `OccupancyRepository.upsert_camera_async` signature and return value to return `CountingCameraItem`. - Replaced raw dictionary payloads with `CountingCameraItem` instances when deactivating obsolete cameras in `OccupancyManager.sync_cameras_from_artemis_async`. 2. **Standards — Smells & Domain Consistency**: - Added `is_counted` property directly on `CountingCameraItem` and updated `_is_counted_camera` to delegate to it. - Replaced magic float `0.001` in `tests/test_trust_dataset_parity.py` with domain constant `CYCLE_END_EPSILON` from `app.facility_time`. 3. **Spec — Window-End Convention Parity**: - Aligned `AnalyticsService.get_cycle_timeseries_async` to query `[cycle.start, cycle.end]` using the inclusive `<= ?` convention while sizing bucket arrays using `cycle.next_start`, preventing boundary event leakage into the 25th bucket. - Enhanced `test_window_bounds_match_at_the_cycle_edges` in `tests/test_trust_dataset_parity.py` to verify that both `get_hourly_flow_distribution_async` and `get_bucketed_cycle_flow_async` match identical bucket distributions and exclude events at `cycle.next_start`. All checks, linters (`ruff`), and full test suites (`pytest` 336 passed, `node --test` 80 passed) are green.

gabogg added 1 commit 2026-09-25 19:22:44 +00:00

Merge remote-tracking branch 'origin/master' into fix/occupancy-review-followups-53-54 ... 8b58997b75

# Conflicts:
#	app/schemas/occupancy_models.py

gabogg merged commit ecbacd9183 into master 2026-09-25 19:22:59 +00:00

gabogg referenced this pull request from a commit 2026-09-25 19:23:00 +00:00

Merge pull request 'fix(occupancy): address review follow-ups from PR #53 and #54 (#65, #66)' (#117) from fix/occupancy-review-followups-53-54 into master

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

blocked

Waits on the issues listed in its "Blocked by:" line before implementation

  

bug

Category: something is broken; behaviour differs from the spec or docs

  

enhancement

Category: new feature or improvement, including refactors, chores and docs

  

high-priority

Address before ordinary-priority work; independent of triage readiness and blockers

  

low-priority

Address after ordinary-priority work; independent of triage readiness and blockers

  

needs-info

Waiting on reporter for more information

  

needs-triage

Maintainer needs to evaluate this issue

  

ready-for-agent

Fully specified, ready for an AFK agent

  

ready-for-human

Requires human implementation

  

referenced

Previously closed issue reopened or referenced by an open issue; visible history marker

  

research

Needs investigation (internet or local resources) before it can be triaged down; used alongside a category and a triage role

  

wontfix

Will not be actioned

No labels

blocked

bug

enhancement

high-priority

low-priority

needs-info

needs-triage

ready-for-agent

ready-for-human

referenced

research

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gabogg/hikcentral!117

No description provided.