Issues 199 (resolved: a node-scoped seat's verb through the console) and 200 (the controller's answer to a long console call is refused by the bus)
#288
Two found while landing ADR 0169. 199: the console left node-scoped seats out of its listing, so a seat's verb never resolved as one and the refusal named the wrong cause — fixed in mesh-tools 27, resolved on open. 200: the bus refuses the controller's reply to the console's inbox on long calls (push of a large machine, issue), so a call that succeeded reads as a timeout — open, located nowhere yet, the bus log line quoted. Numbers 199 and 200 are free across main and open PRs at 13:10Z.
Two found while landing ADR 0169. 199: the console left node-scoped seats out of its listing, so a seat's verb never resolved as one and the refusal named the wrong cause — fixed in mesh-tools 27, resolved on open. 200: the bus refuses the controller's reply to the console's inbox on long calls (`push` of a large machine, `issue`), so a call that succeeded reads as a timeout — open, located nowhere yet, the bus log line quoted. Numbers 199 and 200 are free across main and open PRs at 13:10Z.
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.
Two found while landing ADR 0169. 199: the console left node-scoped seats out of its listing, so a seat's verb never resolved as one and the refusal named the wrong cause — fixed in mesh-tools 27, resolved on open. 200: the bus refuses the controller's reply to the console's inbox on long calls (
pushof a large machine,issue), so a call that succeeded reads as a timeout — open, located nowhere yet, the bus log line quoted. Numbers 199 and 200 are free across main and open PRs at 13:10Z.