Skip to content

Validate requested time after immediate activation - #910

Open
iibaranov-IG wants to merge 1 commit into
AMWA-TV:masterfrom
iibaranov-IG:fix/is05-active-requested-time
Open

iibaranov-IG wants to merge 1 commit into
AMWA-TV:masterfrom
iibaranov-IG:fix/is05-active-requested-time

Conversation

@iibaranov-IG

@iibaranov-IG iibaranov-IG commented Sep 3, 2026 •

Copy link
Copy Markdown

Summary

  • validate that /active reports a non-null TAI requested_time after an immediate activation
  • require requested_time to be no later than activation_time
  • reject missing or malformed activation timestamps without raising an exception
  • update the mock Node so PATCH /staged retains its null requested_time, while GET /active reports an activation timestamp
  • add focused regression tests for immediate and scheduled activation semantics

Validation

At signed commit 1aed76331be399119fbe2a221fcedd94a1db7ac6:

  • .venv/bin/python -m unittest discover -s tests -v — 5 tests pass
  • .venv/bin/flake8 nmostesting/IS05Utils.py nmostesting/mocks/Node.py tests/test_is05_utils.py
  • Python bytecode compilation for all changed Python files
  • git diff --check

Closes #840

@iibaranov-IG
iibaranov-IG force-pushed the fix/is05-active-requested-time branch from e040600 to 1aed763 Compare September 8, 2026 14:34

This branch has not been deployed

No deployments
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.

[IS-05] test_25 doesn't check for requested_time in /active endpoint

1 participant