Relay activation logged as deactivate_relay due to hardcoded activity type #13

New Issue

2026-04-15T08:31:52Z

userAdityaa commented

2026-04-15 08:31:52 +00:00

Summary

Relay status updates use a helper that accepts activity_type, but the helper currently hardcodes deactivate_relay when inserting activity rows. This causes activation actions to be logged as deactivation, corrupting activity semantics and hiding
coupling with infra sync triggers.

Observed behavior

Calling activate_relay updates relay status to active, but activity row is inserted with deactivate_relay.
Activity feed can show deactivation semantics for activation flows.

Expected behavior:

set_relay_status should insert the provided activity_type.
activate_relay should log activate_relay.
infra sync trigger rules should be explicit and not depend on mislabeled activity.

### Summary Relay status updates use a helper that accepts `activity_type`, but the helper currently hardcodes `deactivate_relay` when inserting activity rows. This causes activation actions to be logged as deactivation, corrupting activity semantics and hiding coupling with infra sync triggers. ### Observed behavior * Calling activate_relay updates relay status to active, but activity row is inserted with deactivate_relay. * Activity feed can show deactivation semantics for activation flows. ### Expected behavior: * `set_relay_status` should insert the provided activity_type. * `activate_relay` should log activate_relay. * infra sync trigger rules should be explicit and not depend on mislabeled activity.

userAdityaa referenced a pull request that will close this issue

2026-04-15 09:39:51 +00:00

fix: respect activity_type in set_relay_status and include activate_relay #14

hodlbod closed this issue

2026-04-15 20:39:06 +00:00

Sign in to join this conversation.