feat: add listActiveQueries and cancelActiveQuery for running SQL queries

[krinart]

Summary

Adds SpiceClient.listActiveQueries() (GET /v1/sql/active) and SpiceClient.cancelActiveQuery(queryId) (POST /v1/sql/{id}/cancel) to inspect and cancel synchronous queries running on the runtime.

Test plan

• New unit tests (ActiveQueriesTest) against a local mock HTTP server, covering success, error-status handling, and client-side validation of the query ID.
• mvn compile and the new test suite pass locally.

[Copilot]

Pull request overview

Adds APIs for listing and cancelling active synchronous SQL queries.

Changes:

• Adds ActiveQuery and client operations.
• Adds HTTP mock-based unit tests.
• Documents active-query management.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 6 comments.

File	Description
SpiceClient.java	Implements list and cancel operations.
ActiveQuery.java	Defines active-query metadata.
ActiveQueriesTest.java	Tests requests, responses, and validation.
README.md	Documents API usage and scope.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (3)

src/main/java/ai/spice/SpiceClient.java:1712

• This concatenates the base URI, so a supported address ending in / produces //v1/sql/.../cancel and misses the runtime route. buildProbeRequest explicitly uses URI.resolve to avoid this case; resolve the cancellation path as well.

                    .uri(new URI(String.format("%s/v1/sql/%s/cancel", this.httpAddress, queryId)))

src/main/java/ai/spice/SpiceClient.java:1670

• A successful response with a missing or non-array queries member is reported as “no active queries.” That hides an incompatible or malformed runtime response even though this public method promises to throw for unexpected responses; reject the invalid shape instead of silently returning an empty result.

        if (queries == null || !queries.isJsonArray()) {
            return Collections.emptyList();

src/main/java/ai/spice/SpiceClient.java:1619

• buildProbeRequest does not set a per-request timeout, so after a TCP connection succeeds this synchronous call can wait indefinitely if the runtime never sends a response. Cancellation and refresh both apply HTTP_REQUEST_TIMEOUT; the listing request needs the same bound.

            HttpRequest request = buildProbeRequest(this.httpAddress, "/v1/sql/active", this.apiKey);

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (3)

src/main/java/ai/spice/SpiceClient.java:1707

• Non-object entries are silently dropped, turning a malformed response into an incomplete active-query list. Reject these entries instead; otherwise callers may be told that a running query does not exist and lose the ability to cancel it.

        for (JsonElement element : queries.getAsJsonArray()) {
            if (element.isJsonObject()) {
                result.add(GSON.fromJson(element, ActiveQuery.class));
            }
        }

src/main/java/ai/spice/SpiceClient.java:1700

• The endpoint contract always returns a queries array, so treating a missing member as an empty result silently accepts a malformed or incompatible 200 response. That can report “no active queries” when the response was not actually valid; reject an absent member just as this method already rejects a non-array member.

This issue also appears on line 1703 of the same file.

        if (queries == null) {
            return Collections.emptyList();

README.md:432

• This example throws IndexOutOfBoundsException whenever there are no active queries, which is a normal result of listActiveQueries(). Guard the cancellation so the documented usage is safe to copy.

client.cancelActiveQuery(queries.get(0).getQueryId());

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (3)

Previously missed (2) — in code that hasn't changed since the last review.

src/main/java/ai/spice/SpiceClient.java:1685

• This omits the unauthenticated case: when the runtime establishes no principal, requests share the public scope, so separate clients without credentials can list the same queries. Documenting that boundary avoids implying isolation for no-credential clients.

This issue also appears on line 1795 of the same file.

     * Results are scoped to the authenticated principal — an API key or client
     * certificate — not to this {@code SpiceClient}: every client presenting the
     * same credential lists the same queries. Results also cover only the one
     * runtime instance this client's HTTP endpoint reaches, which behind a load
     * balancer may not be the instance that received a particular query.

README.md:480

• This security-boundary summary is incomplete for clients configured without credentials. Such requests share the runtime's public scope, allowing unauthenticated clients to list and cancel one another's public queries; please state that explicitly.

Both calls are scoped to the authenticated API key or client certificate — not to this
`SpiceClient` instance — and reach only the one runtime process behind this client's HTTP
endpoint, which matters if that endpoint is a load balancer in front of several runtimes.
Runtime releases up to and including v2.1.5 do not scope either endpoint at all — every
caller sees and can cancel every query regardless of credential.

src/main/java/ai/spice/SpiceClient.java:1799

• The cancellation scope also needs to describe unauthenticated requests. They share the runtime's public scope, so one no-credential client can cancel a public query submitted by another; the current wording only explains credentialed callers.

     * {@code queryId} comes from {@link #listActiveQueries()}. Cancellation is
     * scoped to the authenticated principal, not to this {@code SpiceClient}: any
     * client presenting the same credential can cancel the query, while an ID
     * outside that scope is reported as not found. Like
     * {@link #listActiveQueries()}, this reaches only the one runtime instance