Found on the live console: mesh_overview reported mesh-controller on novox as not answering, though it answers. The controller announces the mesh-controller seat without a machine (the seat is the mesh's), and the not-answering check required an announcement naming the machine. An announcement that names no machine now answers for wherever its module is assigned. The test's fake controller now announces as the live one does; the assertion fails without the fix.
Found on the live console: `mesh_overview` reported `mesh-controller on novox` as not answering, though it answers. The controller announces the mesh-controller seat without a machine (the seat is the mesh's), and the not-answering check required an announcement naming the machine. An announcement that names no machine now answers for wherever its module is assigned. The test's fake controller now announces as the live one does; the assertion fails without the fix.
The controller announces the mesh-controller seat without a machine — the seat is the mesh's — and
the console then reported it as not answering on the machine it is assigned to. An announcement that
names no machine now answers for wherever its module is assigned.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found on the live console:
mesh_overviewreportedmesh-controller on novoxas not answering, though it answers. The controller announces the mesh-controller seat without a machine (the seat is the mesh's), and the not-answering check required an announcement naming the machine. An announcement that names no machine now answers for wherever its module is assigned. The test's fake controller now announces as the live one does; the assertion fails without the fix.