Repository navigation
test(e2e): stagehand MQTT state and hot list - #572
Merged
Merged
Conversation
… alert The module list was cached on a system's first alert and never refreshed, so a module added to the system afterwards could never raise an alert. On a miss the list is now fetched again, at most every 5 seconds, and the alert list is checked again once that window has passed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…stack The stack now runs source and mosquitto (with rest-api auth, as deployed), seeds a Broker for source and a state harness driver from PlaceOS/drivers, and serves stagehand for a new `local` Playwright project. The specs hold the broker to the truth: what a fresh client is handed for a system must equal what its modules, names, zones and state imply. They cover publishing, the hot list, reorder, removal, module and system delete, rename, moving a system between levels and cleared statuses. The lifecycle specs need PlaceOS/source v1.22.1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
End-to-end coverage for stagehand's MQTT path, against the local PlaceOS stack:
e2e/stacknow runssourceandmosquitto(rest-api auth, as deployed).up.shseeds a Broker for source (API key, Support) and the stagehand OAuth app. It also seedsplace/e2e/state_harness.crfrom PlaceOS/drivers master: a UDP device whose statuses are set throughexec. A harness the build farm can't build fails only the stagehand specs, not the bring-up.apps/stagehand/e2e/local, newlocalPlaywright project):Backend dependency
The lifecycle specs need PlaceOS/source v1.22.1 (PlaceOS/source#65), which fixes the field reports: alerts for deleted modules, and alerts on the old index after a reorder.
latest(placeos-2.2610.1) doesn't have it yet. Until it does, run withE2E_SOURCE_IMAGE=placeos/source:nightlyor a local build (seee2e/README.md, "MQTT"). The advisory CI job runs only the workplace suite, so it isn't affected. It does bring up the extra services and seed the harness.Testing
localsuite: 15/15 on repeated runs against source with Build Alert Dashboard #65, and again with fix(mqtt): keep startup memory and time flat on large estates source#66 (startup memory). Againstplaceos-2.2610.1, the lifecycle specs and SH-HOT-02 are red.Coverage and gaps are in
E2E_USER_STORIES.md§5. Not covered: a status with a TTL that expires in redis keeps its last value on the broker.🤖 Generated with Claude Code