Skip to content

Feat/reset wipe#55

Open
lazToum wants to merge 5 commits into
devfrom
feat/reset-wipe
Open

Feat/reset wipe#55
lazToum wants to merge 5 commits into
devfrom
feat/reset-wipe

Conversation

@lazToum

@lazToum lazToum commented Jun 5, 2026

Copy link
Copy Markdown
Member

Summary

Makes all six reset-dropdown scopes (chat / metrics / spawns / state / logs / all) work end-to-end and behave consistently. Key fix: the reset fetch was missing the ingress prefix, so under HA every button 404'd. Also makes metrics reset visible live (zeros running actors' in-memory counters), clears the feed buffer on logs, and narrows chat so it only touches chat history.

Tested: chat + metrics verified live (metrics needs a server restart to load this build, since Python isn't hot-reloaded); frontend 513 tests, backend reset 27 + cost/history 46 green.

lazToum added 4 commits June 3, 2026 11:11
  - Route the reset fetch through __WACTORZ_INGRESS_PATH so every scope works
    under HA ingress (was a bare /api/reset → 404 under ingress).
  - metrics scope now also zeroes live in-memory counters (cost, tokens,
    messages_processed) on running actors, so the overview updates immediately
    instead of waiting for a restart.
  - logs scope clears the in-memory log_feed buffer so a refreshed client
    doesn't replay truncated lines.
  - Narrow the chat scope so clearing chat history no longer zeros cost/message
    counters or wipes the alerts/activity feed (that cleanup is metrics-only).
  - Refresh two stale ws.test cases to current reset behaviour (all →
    af-wipe-all) and add backend tests for the metrics/logs/chat changes.

  Includes rebuilt frontend static assets.
@amaliacontiero

Copy link
Copy Markdown
Member

Warning to code reviewers: We decided to withold merge into dev until after 0.5.0's release in main. (est ~June 15th)
Do not merge before then.

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