Skip to content

Fix reduce_detections isinstance np.int32 check and update test documentation - #254

Open
ManupaKDU wants to merge 2 commits into
devfrom
fix-reduce-detections-tests-7736248553300896904
Open

ManupaKDU wants to merge 2 commits into
devfrom
fix-reduce-detections-tests-7736248553300896904

Conversation

@ManupaKDU

Copy link
Copy Markdown

Fix np.int32 check in reduce_detections causing test failures and update test documentation

  • Fixed reduce_detections in frigate/util/object.py to use (int, np.integer) instead of strictly np.int32 to properly handle non-maxima suppression indices across different OpenCV and Numpy versions.
  • Executed local tests natively with fallback mocks for dependency verification.
  • Ran frontend Vitest suite fully successfully.
  • Executed cargo test for all Rust components fully successfully.
  • Updated documentation in .zektopic/status.md, .zektopic/optimization_and_issues_report.md, Jules/improvements.md, and Jules/optimization_and_issues_report.md regarding test outcomes, mocking limitations, and frontend toolchain configurations.

PR created automatically by Jules for task 7736248553300896904 started by @manupawickramasinghe

…ate test documentation

- Fixed `reduce_detections` in `frigate/util/object.py` to use `(int, np.integer)` instead of strictly `np.int32` to properly handle non-maxima suppression indices across different OpenCV and Numpy versions.
- Executed local tests natively with fallback mocks for dependency verification.
- Ran frontend Vitest suite fully successfully.
- Executed `cargo test` for all Rust components fully successfully.
- Updated documentation in `.zektopic/status.md`, `.zektopic/optimization_and_issues_report.md`, `Jules/improvements.md`, and `Jules/optimization_and_issues_report.md` regarding test outcomes, mocking limitations, and frontend toolchain configurations.

Co-authored-by: manupawickramasinghe <73810867+manupawickramasinghe@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions

Copy link
Copy Markdown

PR template validation notice

The PR description could not be validated against the pull request template.

Items to review:

  • Missing section: ## Proposed change
  • Missing section: ## Type of change
  • Missing section: ## AI disclosure
  • Missing section: ## Checklist
  • The Proposed change section is empty. Please describe what this PR does.

Please consider updating your PR description to include all required sections from the template.

…object.py

- Replaced `list[list[int] | tuple[int, ...]]` with `Sequence[list[int] | tuple[int, ...]]` to satisfy strict typing rules via mypy.
- Verified using `mypy --config-file frigate/mypy.ini frigate/util/object.py`

Co-authored-by: manupawickramasinghe <73810867+manupawickramasinghe@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant