Skip to content

Run bounded administration across registered cells - #775

Draft
zlareb1 wants to merge 151 commits into
mainfrom
feat/cell-each
Draft

zlareb1 wants to merge 151 commits into
mainfrom
feat/cell-each

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Related: #735

Changelog category (leave one):

  • New Feature

Changelog entry (one or two sentences a user of Loom can read without the diff; the release pull request collects these into the release notes):

loom cell each runs supported administration commands across registered cells and records each result in a private resumable outcome file. loom cell automation verifies the automation and recovery keys before registering their public identities.

Why

Administration that applies to a deployment must reach every cell without granting the router access to cell private keys. The coordinator uses the directory's current identities and each cell's existing authentication and administration owners. An uncertain mutation stops automatic continuation rather than being replayed.

Scope and risk

  • Add a serial coordinator with a closed command set: live settings list, set, reset and history; signing-key list, rotate and retire; global subject revocation; namespace rate limits; operation and consumer budgets; global blacklist add and list. Global blacklist removal remains unavailable.
  • Add fixed cell administration capability and action routes with closed request models. Target context binds the cell, deployment and bot; action context also carries the run identity, attempt and command digest. The coordinator compares configuration digests and directory generation through census and point reads; fresh admission is not atomic with later business effects. Bodies, response bytes, rows, rounds and operation time are bounded.
  • Add authenticated router reads for the complete cell census, one target and a cell's own public administration identities. A fenced operator write records only the two public bot names and key thumbprints, with an audit in the same transaction.
  • Verify the normal short-lived bot token and its registered proof key for each target. The router operator token stays at the router. Each private key and cell token stays bound to its exact cell origin; redirects and ambient proxies are disabled.
  • Cell-to-router authority reads use verified operating-system CA trust, including an operator-supplied SSL_CERT_FILE, with proxies and redirects disabled. The command's explicit ca_file remains separate from server trust.
  • Share existing settings, signing, revocation, rate, budget and blacklist owners. A partial subject revocation remains incomplete. Ordinary blacklist removal writes a complete selected row with a strictly newer version, preserving its other fields; unrepresentable versions or incompatible replacement storage refuse before writing. The authorized org, namespace and scope remain pinned on the fresh read. Global removal remains unavailable.
  • Persist confirmed completions and refuse ambiguous dispatches on resume. A changed or missing target, incomplete census, unsafe credential file or unsupported capability refuses the run.

The main risks are incorrect bot grants, a directory change during a run, partial business effects and an unknown response after dispatch. The command checks the current target before each attempt and after the run. Operators must inspect ambiguous effects through the recovery procedure; the outcome file is not an idempotency guarantee.

Compatibility, rollout and rollback

  • Wire: add the versioned fixed administration routes and router administration reads/write described in docs/operations/cell-administration.md and the generated HTTP reference. The Python administration route table is generated with them. Existing data-plane operation fields are unchanged.
  • LOOM_MAX_REQUEST_BYTES=0 disables the global body cap; fixed cell administration caps still apply. No new setting or database migration is added.
  • Operator steps: upgrade the router and target cells, provision distinct automation and recovery bots with their approved keys and grants, then register the public pair with loom cell automation. Supply a private credential manifest and outcome path to loom cell each.
  • Rollback removes the new command and routes. Public bot metadata and completed administration effects remain. Preserve private outcome files and inspect uncertain mutations before retrying through another procedure.

Tests

  • The hosted coverage job on the preceding pushed head passes the unchanged rate-limiter branch floor. The older 84.7% result against the 91% floor remains a failure. Twenty-eight reachable guard and actual-owner cases plus two HTTP controls pass locally; they cover class and bucket bounds, override limits, shared-backend identity, storage acknowledgement and checks before local adoption. Both owner checks around storage remain.
  • The preceding pushed head’s Postgres 16 and 18 authority jobs each pass 841 cases, with one skip and one existing xpass. Each also passes its physical-standby durability case, 354 authenticated isolation cases and six reconciliation cases. The corrected native case compares the exact complete 403 envelope and retains its other twenty-seven assertions, including the unchanged-row readback. Earlier jobs each failed that envelope comparison with 840 passes; those failures remain recorded. These results apply to the preceding CI checkout, before the current SCIM integration.
  • Six directly related existing HTTP classification and refusal-before-business controls pass in 3.45 seconds: pytest -q -n 0 tests/unit/test_error_envelope.py::test_a_coded_http_exception_carries_its_class_and_a_plain_one_is_untouched tests/unit/test_error_envelope.py::test_a_typed_http_error_carries_its_class tests/unit/test_cell_admin_subject_route.py::test_subject_route_refuses_authoff_before_business. These cover the shared envelope and actual authority guard, not the complete native case.
  • The earlier native fixture startup failures are preserved. Two regressions reproduce the rejected empty document prefix while three privacy and storage controls pass; a valid fixture prefix makes those same five settings cases pass. The product validator and native business checks remain intact. This proves fixture settings validity, not native fleet success.
  • The preceding ordinary integration shard containing the unchanged blacklist tombstone regressions passes with 639 passes and 136 skips. Earlier current/future-version and overflow failures remain preserved. The full selected-row comparisons, dominating version checks and no-mutation overflow assertions remain exact. Targeted tombstone and caller outcomes also pass twenty-eight cases; typed refusal, storage-before-adoption and diagnostic privacy controls pass. Diagnostics expose only migration basenames, fixed error classes and bounded numeric database codes.
  • Unused forwarding functions, context constants, a state helper and an input model are removed after independent source review. Fourteen actual outcome and entrypoint cases pass. Existing assertions, the real CLI owner and dispatch remain. The SDK API snapshot and analyzer corpus are regenerated through their actual generators; unchanged inputs remain exact.
  • The SCIM integration retains identity-cache invalidation around both ordinary and bounded service-account revocation writes, including error and cancellation cleanup, and retains the creator-lineage checks. The actual CLI snapshot check passes two cases in 1.35 seconds. All five relevant generators report current outputs; scoped lint, formatting and whole-merge whitespace checks pass. The shared resource guard refused the local eight-case cache/write attempt before imports or execution. All eight cases subsequently pass in the actual hosted unit shard. A local failing-baseline execution is still unrun.
  • The preceding SCIM integration has an independent whole-concern review with no source findings or nits. Its Postgres 16 job fails because local termination of an initialization session does not establish server disconnect; that failure remains recorded. The initializer now awaits bounded public close while it still owns an uncancelled raw session, then always attempts local termination. An already-cancelling acquisition starts no fresh close allowance; interrupted or failed cleanup records unknown closure while preserving the first failure. The immediate native backend/lock assertions and all 45 original assertions remain. Sixteen new causal cases fail on the old product code; those same cases and related pool/owner controls pass on the repair: 62 pass in 1.08 seconds. Scoped lint, format, type and architecture-format checks pass. The two cancellation requests in one control are back-to-back requests, not separately delivered cleanup interruptions.
  • The preceding Cell acceptance job completed all ten arms and its provenance check, then failed the unchanged latency criterion. Recalculation from its retained raw request latencies gives a median p99 difference of 17.885 ms against the 10 ms limit; throughput remains within its limit. Its empty exception ledger is consistent with that completed negative verdict. The latency cause remains unknown, and the cleanup repair does not claim to fix Cell acceptance.
  • This repaired concern changes 95 paths. Its fresh different independent whole-concern review reports no source findings or nits. Actual-source full CI has a failed parser-cost unit check: its Python lane exceeds the unchanged CPU-growth bound. The exact hotspot remains unknown. Both Postgres 16 and 18 authority jobs pass: each reports 845 authority cases, one skip and one existing xpass, plus passing standby placement, authenticated isolation and reconciliation checks. Cell acceptance is still running; the parser-cost failure remains blocking and every required check must pass before merge. Earlier hosted results, failed and superseded runs remain specific to their tested inputs. Unrelated main advancement alone does not require repeating healthy checks.

AI assistance in the code (leave one; writing this description with AI is fine):

  • AI-generated (an agent wrote most of the diff): Claude Code and Codex. Independent reviews check the authentication, bounded operation, resume and tenant-isolation contracts.

  • I can explain every line of this diff and how it interacts with the rest of Loom.

Checklist

  • All eight added cache/write regressions pass in hosted CI; their refused local attempt remains unrun. Existing focused and scoped static results are retained.
  • Required final-head full PR CI and native checks pass.
  • CLI snapshots, SDK administration routes and reference pages are generated.
  • No new migration or plugin version change is required.
  • Docs describe the supported commands, operator steps, refusal and recovery behavior.
  • Commits are signed off.

zlareb1 and others added 30 commits November 16, 2026 21:13
…are takes the same lock

The attach command holds the attach lock on a direct, marked session of the
cell's Postgres for its run and resumes by the directory row and the cell's
mode. It refuses before any write on the stores' identity, the session, the
roles, settings and subscriptions that would let an unchecked writer through,
the database encoding, durability, its own grants, the ClickHouse writers,
the table list and the processes' heartbeats; posts attach/begin; creates the
triggers under the migration lock; in recording scans and writes the tenancy
rows, refusing an org past ORG_MAX_BYTES; commits enforced, proves it durable,
waits out every transaction that could have read recording, rescans, places
every org in batches and marks the cell serving. A refusal after the mode
commit leaves the cell enforced and attaching, and a rerun resumes there.

Prepare refuses a session behind a pooler or a database that is not UTF8,
and takes the attach lock. Doctor runs attach's Postgres reads again and
reads stray orgs with --stray-orgs. instances.read_recent keeps stopped rows
inside the widened window, and PRUNE_AFTER_S names the sweep's hour.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…t gate measured end to end

docs/operations/cell-attach.md is the operator's procedure: the preconditions
attach checks and those it relies on, the flags, the point of no return at the
mode commit, the orgs attach does not place and the manual removal of an org
past the length limit, and doctor's reads after serving. cells.md describes
the first attach as it runs (the lock, the refusals, the trigger pass, the mode
commit and its durable read, step 4's wait, rescan and final checks), with its
stated limits and failure rows. upgrades.md step 18 rotates the ClickHouse
writer credential after the LOOM_CELL rollout. bench/cell_trigger_gate.py
measures memory.set and a delivery-sized insert through an attached cell with
the org triggers on and off; results.md records a local run.

Attach compares the final root-secret fingerprint with the one its begin
wrote, and the nonce cleanup's message names no single command.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…s no boot or insights module

instances.read_recent takes the window it reads back; attach's heartbeat
module computes it from the live window and a stopping process's drain and
retirement budgets. PRUNE_AFTER_S is marked as the contract it is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… in wall time, and says when the mode commit's outcome is unknown

The refusals name every table the trigger pass would alter whose owner role
attach's role is not a member of, before any write; ensure_table and
_run_ddl answer applied, busy or denied, so a denial during the pass refuses
at once rather than after --wait as a busy lock.

--wait is wall time: each bounded wait charges its elapsed time, lock tries
included, and every lock try waits at most what is left; scan time stays
outside it. From the mode commit on, a stop that comes before the durable read
says the commit's outcome is unknown and to rerun attach, for a refusal and
for any other error alike.

The prune-window check runs with the refusals, before any write; an enforced
resume runs one trigger pass; the lock session opens inside the block that
closes it; the durable read retries a timeout or an outage only; refusals
name no command that does not exist.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… the attach docs describe one step numbering and today's procedure

--stray-orgs labels only a spent budget as tables left unchecked; any other
refusal names its table and the read continues. A failed catalog read reports
both of attach's Postgres checks as not read. The runbook and doctor describe
removing a stray or over-long org by hand, and name no command that does not
exist yet.

cells.md labels the first attach's list with the design's step names, so step 1
to step 4 mean the same everywhere, rewrites the stuck-process failure row and
the planned tests for a mode that only rises, and says --wait is wall time. The
trigger-cost harness uses cell_triggers.create_statement and deletes the rows
its inserts wrote.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… inside --wait, and doctor warns on the role it runs as

The mode is taken from the first state read, set to unknown only once the
router accepted attach/enforced, and set from what the durable read saw; an
interrupt prints the mode line and goes on. The trigger DDL's lock bound is
taken after the migration lock, from what --wait has left then. An ended mode
transaction whose lock does not clear refuses, naming its backend. A busy
table's holders come back with ensure_table's answer, and attach says them once
per change rather than a boot's warning a try. Attach counts the role it runs as
among its own; doctor does not. The dead SCIM recheck and the unused scim_ok
parameter are gone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… figures say what they establish

cells.md and the runbook state that attach exempts the role it runs as and
doctor does not. results.md gives the marked batch's per-round changes and
their mean, says the delivery-pass gate is met on the mean but not established
by three rounds alone, and that the memory.set p99 gate is unresolved locally.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…nknown only while a try's UPDATE is out, and a busy migration lock is named

Each trigger and mode-commit try gets a lock wait of at least TRY_FLOOR_MS
before --wait is judged spent, so --wait 0 is one try of each wait with no
retry, and an idle cell attaches with it. The run's mode turns unknown just
before a try sends its UPDATE and back to recording when that try rolls back.
A trigger try that finds the migration lock busy names that lock's holder, in
the retry line and in the refusal. The step-4 watch task is awaited after its
cancel. The ATTACH_LOCK_KEY comment says who holds the lock.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…span on one line inside its list items

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Check each probe privilege separately because a comma-separated privilege list accepts any one of them.

Run the attach integration tests in the Postgres matrix and limit their heartbeat reads to the test's own process IDs while retaining the real queries.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Manage mode and direct-session transactions explicitly so a canceled statement cannot start an unbounded rollback. Roll back ordinary mode statement errors within the try's deadline; terminate synchronously when a try ends with an error or cancellation.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Give each trigger attempt a client deadline covering migration lock acquisition, DDL, commit, rollback and unlock. Use explicit transactions so cancellation terminates the session without waiting for rollback or masking the original error with lock cleanup.

Give gate batch scopes a unique prefix per run so cleanup preserves existing rows.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Count privileges a login can reach through SET ROLE or an ADMIN regrant, including noninherited group grants. Keep the owner exemptions and explicit role allow list.

Repeat the writer, trigger, Postgres catalog and standby checks after the rescan and placement before marking the cell serving. Retain the heartbeat watch and its final wait floor.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Check USAGE of pg_read_all_stats and pg_signal_backend because attach uses their privileges without SET ROLE. Keep MEMBER for the separate untrusted-writer reachability checks.

Refuse noninherited capabilities before attach writes, and explain the inherited grant requirement in the refusal labels and runbook. Test both inherited neighbors and signaling a scratch backend.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Concurrent index builds release the ordinary migration key so a shipped blocking migrator can finish without retaining a snapshot behind the build. Retry from the catalogs and checksum ledger, and acknowledge a WAL fence on recorded reruns.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Claim a fresh directory UUID before acceptance writes, and compare the generation, registration and exact fingerprint pair on control mutations. Keep every local acceptance transaction on its attach-lock backend and stop after a lost session.

The additive router column permits older data-plane reads and inserts. Online control requires turnover of older clients and router handlers; the recovery guide covers claimed state cleanup and offline generation rotation.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Refuse explicit open requests under the guarded attaching row lock, preserving quota atomicity and the durable zero-placement boundary. Inventory control writers and their required boundaries, including dynamic cleanup SQL.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Concurrent index builds release the ordinary migration key so a shipped blocking migrator can finish without retaining a snapshot behind the build. Retry from the catalogs and checksum ledger, and acknowledge a WAL fence on recorded reruns.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Send public driver cancellation before aborting the transport, within one absolute cleanup deadline. Separate borrowed migration execution so its operator keeps sole session supervision. Verify backend lock release and preserve interrupted migration errors.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Send public driver cancellation before aborting the transport, within one absolute cleanup deadline. Separate borrowed migration execution so its operator keeps sole session supervision. Verify backend lock release and preserve interrupted migration errors.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Supervise bounded Postgres phases independently, reserving cleanup inside each
existing deadline. Send public close while query and transaction work are alive,
then cancel and reap within that same bound. Borrowed checks and trigger DDL
leave failed-session cleanup to their owner.

Bound the lock owner's close and preserve its original failure across cleanup
errors or repeated cancellation. Keep wait floors and normal busy retries.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Supervise bounded Postgres phases independently, reserving cleanup inside each
existing deadline. Send public close while query and transaction work are alive,
then cancel and reap within that same bound. Borrowed checks and trigger DDL
leave failed-session cleanup to their owner.

Bound the lock owner's close and preserve its original failure across cleanup
errors or repeated cancellation. Keep wait floors and normal busy retries.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Supervise attach, prepare, removal and backout on their exact lock backend. Keep cleanup inside phase deadlines, forward fatal guard exceptions after close, and retry mode contention only after acknowledged rollback and ownership checks.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep the existing store checks and failure envelope while giving each refused observation its own source site. Protect the native test child with the same kill and wait ownership as neighboring tests.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The initialization server can answer native queries before its final HTTP listener starts. Probe the published endpoint through the existing bounded creator command.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
A zombie leader can still report multiple threads. Keep polling within the existing allowance until the complete asserted exit state is observed.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The fixture owns the child through timeout and cancellation. Keep its existing wait budget and always collect that exact process before store cleanup.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Cancel and join the owned task before dedicated sessions close on an interrupted control operation. Preserve the contention checks and wait allowances.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Give each in-process test its own real gate while keeping shutdown permanent within the scenario. A private patch context preserves the fixture through explicit test monkeypatch cleanup.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
A canceled head-lock query leaves its cancellation mechanism and query plan unknown. Record closed reasons and a bounded fresh planning observation while retaining the original failure and cleanup contract.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep the production query and statement budget while reproducing the shared-identity workload in an isolated temporary table. Exact-row, ordering and identity controls distinguish a timeout from an incorrect match.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Enroll before accepting org work, retain the permanent lifecycle through record cleanup, and preserve the first failure through both store closes. Classify the external feed table builder by its exact SQL sink.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
A large absent batch can merge on a partial identity and exhaust the existing statement budget. Sort complete identities before correlated row locks so the batch cannot flatten into that join. Retain all six tenant predicates, the transaction and lock order, and the unchanged native regression and deadlines.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Register each owned database and session as it is acquired. Attempt every cleanup when setup or teardown fails and preserve the original setup or body error. Keep all native assertions and deadlines unchanged.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
A scan can outlive its ATTACH backend and recreate tenancy through the pool after fenced cleanup. Use the existing owner transaction for each unchanged batch and stop after an unknown commit. Keep synthetic request state scoped in its test, account for the tracker owner, and attempt every native fixture cleanup.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
A stalled backend can outlive bounded client cleanup. Require exact-holder verification when release cannot be proved.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Backend termination can remain unproved after cleanup, and later-cell removal verifies paired stores.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Retain bounded administration, native regression baselines and generated surfaces while adopting the current attachment and lifecycle corrections.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Use a complete principal and healthy control, and give blacklist regressions valid fixture org labels so native execution reaches the intended assertions.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Retain connected-account cleanup before subject-revocation completion and preserve bounded cell actions and native successor regressions.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
@zlareb1
zlareb1 changed the base branch from feat/cell-attach-cli to main November 19, 2026 18:56
Preserve the authorized row fields and refuse an unrepresentable successor before writing. Correct the composed type and snapshot contracts, keep budget validation details private, and report allowlisted metadata for native fixture bootstrap failures.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Remove unused forwarding functions from the intent parser. Keep command
execution and durable state in the modules used by the CLI.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Remove two unused context-key sets. Request construction and exact context
validation continue to share the active context helpers.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Use the active saved-command path for resume and expose only supported
request models. Remove two definitions with no consumers.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Cover capacity and backend preconditions, storage failures and the second
admission check before local adoption. Remove an unreachable duplicate
backend condition while retaining both checks around storage.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The empty prefix fails settings validation before migration starts. Check both private cell environments against the real settings model before native execution.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
The shared HTTP exception handler adds auth classification and non-retryability to coded 403 responses. Keep the native refusal check exact and retain its unchanged-row assertion.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Retain the provisioning invalidation boundary around ordinary and bounded
descendant revocation writes. Keep the complete command surface and
regenerate its CLI snapshots from the merged parser.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Await bounded public close while the failed initializer still owns its raw session. Preserve the original failure and report unknown closure when cancellation or cleanup interrupts disconnect.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant