Once mesh-controller#248 stopped granting the store seat to ace's postgres, that module's runtime image, built before #45, still subscribed the seat's subject. The bus refused it, and the refusal ended the process, so ace's postgres runtime crash-looped. The database container was unaffected.
A tool subscription the grants refuse is now logged and costs only that subject. The module's other tools, handlers and provisioning keep running. This is the same treatment #43 gave announcements for issue 217.
Test: the refusing-bus fixture also denies a seat subject. The runtime logs the refusal, nothing escapes as an unhandled rejection, and the module's other tool still answers. The test fails on main and passes here. The full suite passes, 40 of 40, with both buses.
Once mesh-controller#248 stopped granting the store seat to ace's postgres, that module's runtime image, built before #45, still subscribed the seat's subject. The bus refused it, and the refusal ended the process, so ace's postgres runtime crash-looped. The database container was unaffected.
A tool subscription the grants refuse is now logged and costs only that subject. The module's other tools, handlers and provisioning keep running. This is the same treatment #43 gave announcements for issue 217.
Test: the refusing-bus fixture also denies a seat subject. The runtime logs the refusal, nothing escapes as an unhandled rejection, and the module's other tool still answers. The test fails on main and passes here. The full suite passes, 40 of 40, with both buses.
After the controller stopped granting a mesh seat to claimants that do not hold it, an image built
before the runtime followed its membership still subscribed the seat's subject, and the refusal
ended the process: ace's postgres runtime crash-looped. A subject the grants leave out now costs
that subject only, as an announcement's already did (issue 217).
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.
Once mesh-controller#248 stopped granting the store seat to ace's postgres, that module's runtime image, built before #45, still subscribed the seat's subject. The bus refused it, and the refusal ended the process, so ace's postgres runtime crash-looped. The database container was unaffected.
A tool subscription the grants refuse is now logged and costs only that subject. The module's other tools, handlers and provisioning keep running. This is the same treatment #43 gave announcements for issue 217.
Test: the refusing-bus fixture also denies a seat subject. The runtime logs the refusal, nothing escapes as an unhandled rejection, and the module's other tool still answers. The test fails on main and passes here. The full suite passes, 40 of 40, with both buses.