Skip to content

test: ask zm-api for deleted monitors in the live deleted-monitor test - #64

Merged
SteveGilvarry merged 1 commit into
ZoneMinder:mainfrom
nabbi:test/live-v3-deleted-monitors
Oct 27, 2026
Merged

SteveGilvarry merged 1 commit into
ZoneMinder:mainfrom
nabbi:test/live-v3-deleted-monitors

Conversation

@nabbi

@nabbi nabbi commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

Automated PR, tested in a zm-holodeck sandbox. An AI agent (Claude Opus 5.5) ran the live suite against a disposable lab (ZoneMinder upstream master 260a47518 plus pending fixes, API v2 served by zm-php-api, zm-api master acae7ae next to it, passive; simulated HikVision, Dahua, Axis, Reolink and ONVIF cameras). Minimal human review before opening: please review it as you would any contributor's PR.

TL;DR

  • What: test_deleted_monitors_hidden[v3] always skips. zm-api leaves soft-deleted monitors (Deleted = 1) out of GET /api/v3/monitors unless include_deleted=true is passed, so the test never finds one, even on a server that has some
  • Change: the test's raw v3 listing passes include_deleted="true", then checks that get_monitors() still leaves those monitors out. The v2 path and the library code are unchanged; 1 file, +2/-1
  • Risk: tests only. Without a deleted monitor on the server the test still skips, as before
  • Tested: live suite with a soft-deleted monitor present: on main 2ff846a v2 passed and v3 skipped ("the server has no deleted monitor"); with this change both passed. Full live suite with writes, both APIs: 50 passed, 4 skipped, 0 failed. ruff, ruff format, mypy pass

🤖 Generated with Claude Code

zm-api leaves soft-deleted monitors out of api/v3/monitors unless
include_deleted is set, so on API v3 the test never found one and
always skipped, even on a server that has some. It now asks for them,
and checks that get_monitors still leaves them out.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@SteveGilvarry
SteveGilvarry merged commit e9a5b9c into ZoneMinder:main Oct 27, 2026
3 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 27, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants