@meshmakers/octo-services 3.4.1160 → 3.4.1190
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -55586,6 +55586,11 @@ interface TusUploadOptions {
|
|
|
55586
55586
|
*/
|
|
55587
55587
|
restoreArchiveData?: boolean;
|
|
55588
55588
|
onProgress?: (bytesUploaded: number, bytesTotal: number) => void;
|
|
55589
|
+
/**
|
|
55590
|
+
* Status callback for the phase after the upload: invoked when the restore-job start is being
|
|
55591
|
+
* retried (see the 403 retry on `startUpload`), so a progress UI can say why nothing moves.
|
|
55592
|
+
*/
|
|
55593
|
+
onStatus?: (statusText: string) => void;
|
|
55589
55594
|
}
|
|
55590
55595
|
interface TusUploadResult {
|
|
55591
55596
|
jobId: string;
|
|
@@ -55594,7 +55599,22 @@ declare class TusUploadService {
|
|
|
55594
55599
|
private readonly httpClient;
|
|
55595
55600
|
private readonly configurationService;
|
|
55596
55601
|
private readonly authorizeService;
|
|
55602
|
+
/**
|
|
55603
|
+
* Delays between retries of a restore-job start that answered 403 (AB#5227). The bot service's
|
|
55604
|
+
* tenant gate authorizes a parent administrator against an EXISTING child tenant, and its
|
|
55605
|
+
* hierarchy answer is cached for up to 60 seconds — so a restore right after (re-)creating the
|
|
55606
|
+
* tenant can be refused although the tenant is there. The ladder spans ~75s, one TTL plus slack.
|
|
55607
|
+
* A genuine permission denial still fails, after the ladder, with the server's own reason.
|
|
55608
|
+
* Overridable so specs don't wait.
|
|
55609
|
+
*/
|
|
55610
|
+
restoreForbiddenRetryDelaysMs: number[];
|
|
55597
55611
|
startUpload(options: TusUploadOptions): Promise<TusUploadResult>;
|
|
55612
|
+
/**
|
|
55613
|
+
* Starts the restore job, retrying a 403 across the tenant-hierarchy cache TTL (see
|
|
55614
|
+
* {@link restoreForbiddenRetryDelaysMs}). Only the job start is retried — the uploaded artifact
|
|
55615
|
+
* is already staged, so no bytes are re-transferred. Every other error propagates immediately.
|
|
55616
|
+
*/
|
|
55617
|
+
private startRestoreJobWithForbiddenRetry;
|
|
55598
55618
|
private performTusUpload;
|
|
55599
55619
|
/**
|
|
55600
55620
|
* Starts the restore job for the uploaded artifact.
|