Skip to content

fix: address simple PRT3 review follow-ups#599

Open
yozik04 wants to merge 1 commit into
devfrom
pr3_followups
Open

fix: address simple PRT3 review follow-ups#599
yozik04 wants to merge 1 commit into
devfrom
pr3_followups

Conversation

@yozik04
Copy link
Copy Markdown
Collaborator

@yozik04 yozik04 commented May 13, 2026

Bundle of low-risk PRT3 follow-ups from the PR #596 review:

  • M1 silent drop of unmapped element events: drop manual existence guard in _apply_prt3_event_change so fire-alarm/zone events for unlabeled zones beyond PRT3_MAX_ZONES are still applied (MemoryStorage already auto-creates).
  • M2 retried panic/arm can double-fire: set retries=1 on send_panic and control_partitions; these commands are not idempotent and a retry after a lost echo can re-trigger panic or move arm state twice.
  • M4 startup label-load worst case: extend startup warning to cover PRT3_MAX_USERS + PRT3_MAX_AREAS as well as zones.
  • M5 user code in packet dumps: redact AA/AD payloads at the protocol layer when LOGGING_DUMP_PACKETS is enabled; previously only the panel-layer logs were redacted.
  • Minor: accept &fail case-insensitively for symmetry with &OK/&ok.
  • Minor: remove dead EVENT_MAP/PRT3Event imports from prt3/panel.py.
  • Minor: fix pre-existing "definitons_loaded" subscriber typo (publisher sends "definitions_loaded").
  • Also: convert two pre-existing lambdas to defs and remove two unused imports to clear flake8 in touched files.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

Bundle of low-risk PRT3 follow-ups from the PR #596 review:

- M1 silent drop of unmapped element events: drop manual existence guard
  in _apply_prt3_event_change so fire-alarm/zone events for unlabeled
  zones beyond PRT3_MAX_ZONES are still applied (MemoryStorage already
  auto-creates).
- M2 retried panic/arm can double-fire: set retries=1 on send_panic and
  control_partitions; these commands are not idempotent and a retry
  after a lost echo can re-trigger panic or move arm state twice.
- M4 startup label-load worst case: extend startup warning to cover
  PRT3_MAX_USERS + PRT3_MAX_AREAS as well as zones.
- M5 user code in packet dumps: redact AA/AD payloads at the protocol
  layer when LOGGING_DUMP_PACKETS is enabled; previously only the
  panel-layer logs were redacted.
- Minor: accept &fail case-insensitively for symmetry with &OK/&ok.
- Minor: remove dead EVENT_MAP/PRT3Event imports from prt3/panel.py.
- Minor: fix pre-existing "definitons_loaded" subscriber typo
  (publisher sends "definitions_loaded").
- Also: convert two pre-existing lambdas to defs and remove two unused
  imports to clear flake8 in touched files.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@sonarqubecloud
Copy link
Copy Markdown

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