@uipath/common 1.203.0-preview.205 → 1.204.0-preview.206

package/dist/attachment-binding.d.ts

@@ -32,10 +32,24 @@ export declare const ATTACHMENT_UPLOAD_INSTRUCTIONS = "Check that the active ten
  * the basename when '=' is absent (no binding key required there).
  */
 export declare function parseAttachmentSpec(spec: string): ParsedAttachmentSpec;
+/** A spec whose file has been read: bytes plus the basename used as the upload name. */
+export interface PreparedAttachmentSpec extends ParsedAttachmentSpec {
+    fileName: string;
+    bytes: Uint8Array;
+}
+/**
+ * Phase 1 of {@link resolveAttachmentInputs}: read every spec's bytes before
+ * any network write. Fails fast on the first unreadable or empty file, so a bad
+ * local path never orphans an attachment. Exported on its own for callers that
+ * upload later (agent debug uploads inside its service, after the Studio Web
+ * import). The original error is kept on `cause` so classification can find it.
+ */
+export declare function readAttachmentSpecs(specs: ParsedAttachmentSpec[]): Promise<PreparedAttachmentSpec[]>;
 /**
  * Read each spec's bytes (fail-fast on any error), then upload all via the
  * caller-supplied `upload` function (e.g. `uploadJobAttachment` from
  * `@uipath/orchestrator-sdk`) in parallel. Returns references in input order.
+ * See {@link readAttachmentSpecs} for the read phase.
  *
  * Two-phase to avoid orphaned attachments when a local path is bad: phase 1
  * reads + validates every file before any network write. A read failure

package/dist/error-graph.d.ts

@@ -0,0 +1,37 @@
+/**
+ * Bounded breadth-first walk over `.cause` and `AggregateError.errors`,
+ * yielding each object node once. Node's `fetch` wraps the real failure in a
+ * generic `TypeError: fetch failed` and races (IPv4/IPv6, proxy fallbacks)
+ * collect per-attempt failures in `AggregateError.errors`, so the useful
+ * code can sit anywhere in the graph. The step cap and `seen` guard keep a
+ * pathological/cyclic graph from looping; 32 is far more than any real
+ * failure nests.
+ */
+export declare function walkErrorGraph(error: unknown): Generator<Record<string, unknown>, undefined, undefined>;
+/**
+ * Parse an `HTTP <status>` prefix out of an error message. SDK wrappers often
+ * throw plain `Error`s shaped `HTTP 403: <body>` with no structured status
+ * field; every classifier that treats "has a status" as "the service
+ * answered" must see these too, or the local-vs-service split drifts between
+ * layers. Shared by `extractErrorDetails` and `instructionsFor`.
+ */
+export declare function parseHttpStatusFromMessage(message: string): number | undefined;
+/**
+ * The failing HTTP status found anywhere in the error graph, not just on the
+ * outer node.
+ *
+ * Resolvers and command helpers wrap an SDK error as
+ * `new Error(\`...: ${await extractErrorMessage(err)}\`, { cause: err })`.
+ * That moves the SDK's `status` / `response.status` one or more levels down,
+ * and the `HTTP <status>` token the wrapper splices into its own message is
+ * no longer at the start, so neither `err.status` nor
+ * {@link parseHttpStatusFromMessage} sees it on the outer node — a wrapped
+ * 5xx classified as `unknown_error` / `RetryWillNotFix` instead of
+ * `server_error` / `RetryLater`.
+ *
+ * Only 4xx/5xx count: a 2xx buried in the graph belongs to a call that
+ * succeeded, and the outer node is where a non-failing status would matter.
+ * Used for classification and `Context.httpStatus` only — message building
+ * still reads the outer node, so a wrapper keeps the text it chose.
+ */
+export declare function findHttpStatusInGraph(error: unknown): number | undefined;

package/dist/error-handler.d.ts

@@ -1,4 +1,6 @@
+import { parseHttpStatusFromMessage } from "./error-graph";
 import type { CliErrorCode, ErrorContext, FailureResultType, RetryHint } from "./formatter";
+export { parseHttpStatusFromMessage };
 /**
  * Structured error details returned by {@link extractErrorDetails}.
  */
@@ -101,14 +103,6 @@ export declare function describeConnectivityError(error: unknown): ConnectivityE
  * failures, not the local OS's.
  */
 export declare function describePermissionError(error: unknown): LocalPermissionError | undefined;
-/**
- * Parse an `HTTP <status>` prefix out of an error message. SDK wrappers often
- * throw plain `Error`s shaped `HTTP 403: <body>` with no structured status
- * field; every classifier that treats "has a status" as "the service
- * answered" must see these too, or the local-vs-service split drifts between
- * layers. Shared by {@link extractErrorDetails} and `instructionsFor`.
- */
-export declare function parseHttpStatusFromMessage(message: string): number | undefined;
 export declare function isHtmlDocument(body: string): boolean;
 /**
  * Extract a structured error message and details from an unknown thrown value.