Skip to content

Show how each client fares with the servers in the matrix - #23

Open
bbatsov wants to merge 1 commit into
mainfrom
matrix-clients
Open

bbatsov wants to merge 1 commit into
mainfrom
matrix-clients

Conversation

@bbatsov

@bbatsov bbatsov commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

A check counts for the clients whose code it links to, or for every client when it links to none (e.g. eval.value). Warnings don't count. robust.sessions-at-once links only to CIDER's code, so it counts only for CIDER, although any client sharing a server can end up waiting behind another one.

The matrix page gets a second tab with a row per client, where each
server gets the number of checks it passes out of the ones that would
break the client, with the ones it failed on hover. A check breaks the
clients whose code its refs point at (a client profile's checks point
at their own client), or every client when it points at none (e.g.
eval.value). Warnings break nobody.

JSON reports name the clients of each result, so a report keeps
working with the client profiles of the proof that made it. Clients
come in the order of how many checks they depend on, which puts the
ones proof knows the most about first.

This branch has not been deployed

No deployments
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.

1 participant