Skip to content

Claude/overmanager alert control sync dsu4ko#30

Merged
proofofprints merged 6 commits into
mainfrom
claude/overmanager-alert-control-sync-dsu4ko
Jun 19, 2026
Merged

Claude/overmanager alert control sync dsu4ko#30
proofofprints merged 6 commits into
mainfrom
claude/overmanager-alert-control-sync-dsu4ko

Conversation

@proofofprints

Copy link
Copy Markdown
Collaborator

Summary

Changes

Checklist

  • npx tsc --noEmit passes with no errors
  • cd src-tauri && cargo check passes with no errors
  • New Rust struct fields use #[serde(default)]
  • New Tauri commands are registered in lib.rs invoke_handler!
  • Screenshots attached (if UI changes)

Testing

Related issues

claude added 6 commits June 16, 2026 12:31
…obile

acknowledge_alert previously only flipped the local flag — nothing reached the
cloud, so a read marked on the desktop never showed up on the web portal or
mobile app. It now POSTs the alert's (ruleName, minerIp, timestamp) tuple to
the new /ingest/alert-read endpoint after marking it locally, falling back to
the offline queue (drained by the sync loop) when offline or on failure.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YYr4XG3SBHoSpP33d84Jqa
… queue

acknowledge_alert always returned Ok(()) regardless of whether the cloud
push succeeded, and the success path had no logging at all — making it
impossible to tell from the console whether an ack ever reached the cloud.
Also the offline queue's CHECK constraint never included 'alert-read' (or
'alerts-read-all'), so a queued ack while offline would silently fail to
insert.
…ert-control-sync-dsu4ko

# Conflicts:
#	src-tauri/src/commands/alerts.rs
A 5-minute suppression window after launch made the alerting system look
broken to users who'd just opened the app — no alerts fire, no ack to
test. 30s is enough for a poll cycle or two to establish a baseline for
stateful rules (NoShares, MinerOffline) without the long dead zone.
Elevate the cloud->desktop "no local match" branch from debug to warn
(was indistinguishable from "message never arrived" at default log
level) and log receipt of every alert-read WS message. Also log the
two no-op paths in acknowledge_alert (already-acked, unknown id) that
previously failed silently with zero console output.
@proofofprints proofofprints merged commit 75fb60b into main Jun 19, 2026
1 check passed
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.

2 participants