@apifuse/provider-sdk 2.1.0-beta.0 → 2.1.0-beta.10

package/src/runtime/executor.ts

@@ -1,7 +1,15 @@
-import { ProviderError } from "../errors";
+import { ProviderError, SessionExpiredError } from "../errors";
 import { parseSchema } from "../schema";
 import type { ProviderContext, ProviderDefinition } from "../types";
 
+export function isStreamingOperation(
+	provider: ProviderDefinition,
+	operationId: string,
+): boolean {
+	const kind = provider.operations[operationId]?.transport?.kind ?? "json";
+	return kind !== "json";
+}
+
 /**
  * Execute a provider operation by calling its handler.
  *
@@ -40,10 +48,31 @@ export async function executeOperation(
 
 	const execute = () =>
 		ctx.trace.span(`handler:${operationId}`, () =>
-			operation.handler(ctx, validatedInput),
+			Promise.resolve(operation.handler(ctx, validatedInput)),
 		);
 
-	const result = await execute();
+	let result: unknown;
+	try {
+		result = await execute();
+	} catch (error) {
+		// Session expiry is renewed by Credential Service via the /auth/refresh
+		// route, NOT in-process here: this executor cannot mutate ctx.credential,
+		// so an in-process retry would just repeat the call with the same stale
+		// credential (and risk repeating partial side-effects). Instead we surface
+		// the expiry so Credential Service refreshes and re-drives the operation
+		// with a fresh credential. `retryOnAuthRefresh` declares that this
+		// operation is safe to re-drive after refresh, which we signal by marking
+		// the surfaced error retryable; non-idempotent operations (the default)
+		// stay non-retryable so they are not auto-re-driven. See design.md §4.3 D3.
+		if (error instanceof SessionExpiredError && operation.retryOnAuthRefresh) {
+			throw new SessionExpiredError(error.message, { retryable: true });
+		}
+		throw error;
+	}
+
+	if (isStreamingOperation(provider, operationId)) {
+		return result;
+	}
 
 	return parseSchema(
 		operation.output,