Seen on the bus today once the first modules ran the new runtime: Publish Violation - User "ace.baserow", Subject "$JS.API.DIRECT.GET.ASSIGNMENTS" for every one of them. The runtime asked the stream's root with last_by_subj in the body; the mesh grants a module's account only the subject-addressed form, $JS.API.DIRECT.GET.ASSIGNMENTS.mesh.assignment.<node>.<module>. Every runtime therefore kept the derived shape (the designed fallback, which is why nothing broke and nobody noticed). The request is now the subject-addressed form with an empty body. Membership tests green against a real NATS.
Merge after mesh-controller #194 has rolled: with #193 live, this merge rebuilds the runtime image and its forty-two dependents through the build queue, and #194 is what makes that queue hold.
Seen on the bus today once the first modules ran the new runtime: `Publish Violation - User "ace.baserow", Subject "$JS.API.DIRECT.GET.ASSIGNMENTS"` for every one of them. The runtime asked the stream's root with `last_by_subj` in the body; the mesh grants a module's account only the subject-addressed form, `$JS.API.DIRECT.GET.ASSIGNMENTS.mesh.assignment.<node>.<module>`. Every runtime therefore kept the derived shape (the designed fallback, which is why nothing broke and nobody noticed). The request is now the subject-addressed form with an empty body. Membership tests green against a real NATS.
Merge after mesh-controller #194 has rolled: with #193 live, this merge rebuilds the runtime image and its forty-two dependents through the build queue, and #194 is what makes that queue hold.
The runtime asked the assignments stream's root for the last message by subject in the body, and the
mesh grants a module's account only the subject-addressed form of the direct get — the server refused
every read (Publish Violation on $JS.API.DIRECT.GET.ASSIGNMENTS for every module on the new runtime),
so every runtime kept the derived shape. The address is now the stream then the subject, nothing in the
body, which is the one address the account has.
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.
Seen on the bus today once the first modules ran the new runtime:
Publish Violation - User "ace.baserow", Subject "$JS.API.DIRECT.GET.ASSIGNMENTS"for every one of them. The runtime asked the stream's root withlast_by_subjin the body; the mesh grants a module's account only the subject-addressed form,$JS.API.DIRECT.GET.ASSIGNMENTS.mesh.assignment.<node>.<module>. Every runtime therefore kept the derived shape (the designed fallback, which is why nothing broke and nobody noticed). The request is now the subject-addressed form with an empty body. Membership tests green against a real NATS.Merge after mesh-controller #194 has rolled: with #193 live, this merge rebuilds the runtime image and its forty-two dependents through the build queue, and #194 is what makes that queue hold.