PR Drain
Pull requests converging on master, one at a time.
Every open pull request as the integration lane assessed it: what it waits for, what would move it, what it depends on and overlaps, and the issue it carries.
- Issues ready86plan.status /counts/by_status/READY
- Issues active1plan.status /counts/by_status/ACTIVE
- Issues blocked159plan.status /counts/by_status/BLOCKED
- Issues done161plan.status /counts/by_status/DONE
Issue
One issue of the plan, as the plan records it.
I2487 · development-runtime · p1 · wave 2
A screen is streamed, and one stream tells an open page which readings changed
Send a screen as it becomes known and keep it current without polling: the shell and every panel whose reading is at hand are written at once, a panel whose first reading is pending follows on the same response, and after that one WebSocket subscription tells the page which readings changed.
- Depends on
I2486- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/httpapps/majordomus-cli/src/uiapps/majordomus-cli/src/capability/readings.rsshare/ui/ui.jsdocs/MAJORDOMUS_UI.mdtest/casesand 1 more- Evidence
- 0 of 4
- Started
- not yet
- Verified
- not yet
- Completed
- not yet
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
Pull-request drain
The integration lane asks the forge for every open pull request; this takes a while and arrives after the screen.