mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
pulse-triage[bot]
834fcaeb36
## Outcome This batch makes guest identity persistence safer, keeps broadcast resource rows and their History targets in one captured generation, and makes completed-backup evidence accessible by keyboard and touch. Existing help now explains container CPU scales and passive comparisons. Native macOS guidance checks receive real GNU timeout without replacing unrelated system utilities. The work follows retained identity-write/shutdown failures, fleet CPU and History consistency evidence, inaccessible backup disclosures and confusion about container CPU readings. It improves those existing paths without claiming field recovery or complete performance relief. ## Included reviewed candidates The complete proposed range is `800329cbd83c48fdb7402a18633189f2c8a2d6ff..9b057cb141221526a96fac05bdbdf8ed6e8625fc`: - Guest metadata ordering/coalescing and safe retained shutdown: `244d322dce` and `5e51069048`, integrated at `d7a305922a`. - Native guidance prerequisites: `13f6d10798` and `443faa53b6`, integrated at `f7fca0e164`. - Accessible existing Workloads backup details: `02e6a90374`, integrated at `8661c1fc65`. - Paired complete resource/History capture and faithful full-content controls: `54de7bdca7`, `32f09dc13d`, `8b12e0ee1b`, `d206b03990` and `9cc8523881`, integrated at `2787b4eabd`. - Container CPU documentation: `0c283d2dd5`, integrated at `15e8c5ccf6`. - Router-owned limiter joins and sealed late worker admission: `5b560521e2`. Reviewed identities and authors are unchanged. Current upstream Docker link editing and platform layout repairs are incorporated by an additive full-SHA merge; earlier upstream governance and Kubernetes layout history are retained. The later upstream Docker image badge sizing repair at `800329cbd83c48fdb7402a18633189f2c8a2d6ff` is also retained after one successful bounded refresh and additive merge. ## Behaviour and safeguards Identity polls merge only monitor-owned fields, preserve operator links/tags/notes and OCI classification, and do not spin-retry filesystem failures. Incomplete tenant shutdown retains ownership and prevents directory removal. Router shutdown joins its own limiters without resetting budgets or stopping another Router. Broadcast resources and target mappings are detached together. Health comparison controls use one evaluation instant while production still samples real UTC at the existing boundary. Full-content, overlay/clear, identity and observation-time controls remain. Backup disclosures preserve hover and add keyboard/touch access to the same read-only evidence. CPU guidance distinguishes host-capacity normalisation, VM CPU counts, version-qualified rounding, missing readings and actual alert delivery; it asks for ordinary observations, not forced workload or threshold changes. ## Validation and remaining limits - Provenance, retained ancestry, clean additive merge and whitespace checks pass. - Every unpublished non-merge commit passes the canonical completion/history guard. Final-range browser receipt coverage, public registry audit and contract audit pass. - Accepted candidate evidence includes focused writer/API races, startup observations, vet and actual builds; 363 connected backup frontend tests with four desktop/touch browser cases; CPU help's 132 connected frontend tests, lint/types/build/budgets, focused Go checks and four Docs browser cases. Browser receipts cover unchanged final backup bytes and are not rerun merely because the batch contains several candidates. - Gate frontend proof at `9daeed13`: 246 tests in four connected files, type-check, all lint checks, actual embed build and bundle budgets pass; complete output hash matches and guest stop completes. - Exact refreshed head `9b057cb1` passes 49 Docker native-table and platform-layout guardrail tests (`source-l8diazgn`); complete output and guest stop are verified. This covers the later width-only upstream change without repeating the earlier full frontend checks. - Gate backend attempt `source-pz6qwk2t` fails in guest readiness after capacity waiting, client exit 2, with no command verdict and confirmed guest stop. It is not a test pass and is not replayed. All backend Go source, manifests and native workflow bytes are unchanged from reviewed `5b560521` and its focused races/vet/real-build evidence; that evidence remains usable without inventing an aggregate pass. - The retained broad API ten-minute timeout, earlier drain/startup failures, adverse allocation/frame costs and failed stable RSS retest are not erased by these focused results. Required exact-head CI remains authoritative for landing. - This is not native guest thaw/recovery, PBS badge agreement, CPU/RSS relief, notification delivery or release inclusion. Independent thaw, fresh writes on every covered filesystem, liveness and only-prior-active restoration remain necessary before resuming uncertain monitoring. Related to #2199 Related to #1723 Related to #2439 Related to #2447 [How Pulse handles triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md)
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.