GeezerVison

[qa] Delete only stale topics in the Kafka Avro test's setup

The setup read the variant id where it expected a topic's creation date, so
it deleted every kafka_avro topic on the cluster, including those of runs
still in progress against it, such as the other architecture's job. It now
reads the date that each topic name carries.

Signed-off-by: Leonid Ryzhyk <[email protected]>

Preserve literals in prebuilt binary cache keys

Blind namespace replacement can change SQL literals and conflate distinct
programs. Normalize generated Rust identifiers and Cargo crate references
structurally, including workspace members, while preserving literal data.
Reject duplicate normalized archive paths instead of overwriting them.

Cover namespace independence, literal collisions, Cargo references and
malformed generated sources. The four prebuilt cache tests pass, and real
SQL compiler output normalizes identically across pipeline IDs.

[pipeline-manager] Stream the support bundle while it is collected.

The support bundle handler sent nothing until it had collected all data
and built the whole ZIP file. A slow collection, such as the profile of
a large multihost pipeline in a long commit, kept the response silent
for minutes, so a proxy or the client closed it first.

Now the response starts when the request is valid. When the bundle
collects new data, its first entry is collection_log.txt, which gets a
line every 10 s until the collection is complete. Then the collections
and the metadata follow, each sent when it is written. The ZIP file
uses data descriptors, which the profiler UI, unzip, Python, and the
zip crate read.

A failure after the response starts now cuts the response short
instead of setting an error status. The collection itself reports
failures inside the bundle, as before.

The API docs no longer list 503 examples for a failed pipeline request,
because the endpoint reports such failures inside the bundle. They
describe collection_log.txt and the missing Content-Length. The
operations guide and the changelog describe the change too.

Part of feldera/cloud#2163.

Signed-off-by: Ben Pfaff <[email protected]>

[dbsp] Remove the advanced flag of the circuit metrics

Signed-off-by: Mihai Budiu <[email protected]>

[connectors] Assert the early health check only before the threshold

The timer that reports a long retry loop unhealthy starts at the chunk's
first retry, which is after the test calls `write_batch`. So an instant
taken before that call bounds the timer: while less than the threshold
has passed since then, no report can exist yet, and the assertion holds
by construction. A runner that stalls past the threshold skips the check
instead of failing it, so the test no longer races a wall clock.

Refs #7828.

[fda] Say that a restart loses the transaction status.

A transaction might have committed before the pipeline restarted, so
`commit-transaction` cannot say that the restart lost it.

[SQL] Backport two Calcite fixes

Signed-off-by: Mihai Budiu <[email protected]>

[ci] apply automatic fixes

Signed-off-by: feldera-bot <[email protected]>

[SQL] Forbid comparisons between ROW-typed values in SQL

Signed-off-by: Mihai Budiu <[email protected]>

[web-console] Mock navigating in DeletedPipelineState and check test …

…files load in CI

The DeletedPipelineState integration test reaches sveltekit-superforms 3
through AppHeader > ProfileButton > the API key and OIDC trust forms.
superforms 3 imports `navigating` from `$app/state`, so the import fails
if the mock has no `navigating`.

CI found this only in the Web Console Integration Tests job, which waits
for the Docker build. The new `test-list` script loads the integration
and e2e test files without running them and without a Feldera instance
(`vitest list`, `playwright test --list`). The Web Console Unit Tests job
runs it, so an import error fails CI before the Docker build.

To let the files load without a Feldera instance:
- The integration setup file warms the compilation cache in a
  `beforeAll` hook, because `vitest list` runs no hooks.
- Under CI with no origin configured, `configureTestClient()` installs a
  fetch that fails every request with the "No Feldera origin configured"
  error, instead of throwing when the file loads.
- `playwright.config.ts` calls `configureTestClient()` once. Playwright
  loads the config in the runner and in each worker, so the e2e specs
  and `globalSetup` no longer call it.