From 88bff675e998d16f4a9018b94ff73b769af888ee Mon Sep 17 00:00:00 2001 From: James Maes Date: Tue, 13 Oct 2026 19:58:41 -0500 Subject: [PATCH] fix(attachments): use only qbit-object-storage's api package Stop reading the bucket cap through StorageBucket.config() (the non-api StorageBucketConfig, flagged by the qbit-bom guardrails, G1-arch). Collaboration enforces its per-table cap; object storage still enforces the bucket cap at put time. An api accessor is requested upstream. Co-Authored-By: Claude Opus 5.5 --- .../qbits/collaboration/attachments/AttachmentStorage.java | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/main/java/com/kingsrook/qbits/collaboration/attachments/AttachmentStorage.java b/src/main/java/com/kingsrook/qbits/collaboration/attachments/AttachmentStorage.java index d99acbb..724933d 100644 --- a/src/main/java/com/kingsrook/qbits/collaboration/attachments/AttachmentStorage.java +++ b/src/main/java/com/kingsrook/qbits/collaboration/attachments/AttachmentStorage.java @@ -45,11 +45,14 @@ public class AttachmentStorage } /******************************************************************************* - ** Enforce the bucket's cap as well as collaboration's configured cap. + ** The bucket's own upload cap, when object storage exposes it through its api + ** package. It does not yet (requested from qbit-object-storage), so this + ** returns Long.MAX_VALUE: collaboration enforces its configured per-table cap, + ** and object storage still enforces the bucket's cap when the object is put. *******************************************************************************/ public long maxBytes(String name) { - return (bucket(name).config().getMaxUploadBytes()); + return (Long.MAX_VALUE); } /******************************************************************************* -- 2.54.0