Carries #166 (push manager honours the node role on subscription updates; a node whose id lease was taken claims a fresh id, event cluster.node-id-reassigned) and #167 (pipelined PostgreSQL write batches). Store, IMAP and JMAP suites run against PostgreSQL before landing #167; the one JMAP compliance failure is pre-existing on PostgreSQL (see #167).
Carries #166 (push manager honours the node role on subscription updates; a node whose id lease was taken claims a fresh id, event `cluster.node-id-reassigned`) and #167 (pipelined PostgreSQL write batches). Store, IMAP and JMAP suites run against PostgreSQL before landing #167; the one JMAP compliance failure is pre-existing on PostgreSQL (see #167).
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.
Carries #166 (push manager honours the node role on subscription updates; a node whose id lease was taken claims a fresh id, event
cluster.node-id-reassigned) and #167 (pipelined PostgreSQL write batches). Store, IMAP and JMAP suites run against PostgreSQL before landing #167; the one JMAP compliance failure is pre-existing on PostgreSQL (see #167).