feat: add debugging around production error

we're seeing this error a LOT in production but don't have much information to debug from - add a bit more
storacha · Oct 7, 2024 · e663c06 · e663c06
1 parent 744ca61
commit e663c06
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/upload-api/stores/agent/stream.js b/upload-api/stores/agent/stream.js
@@ -115,9 +115,13 @@ export const assert = async (message, { stream, store }) => {
       // 🔬 Need to figure if there are consumers downstream that depend on
       // having invocation details in the stream record and whether we can
       // safely remove it because this additional IO which seems unnecessary.
-      const { ok: invocation } = await Store.getInvocation(store, task)
+      const result = await Store.getInvocation(store, task)
+      const { ok: invocation } = result
       if (!invocation) {
-        throw new NoInvocationFoundForGivenReceiptError()
+        console.error(result.error)
+        throw new NoInvocationFoundForGivenReceiptError(
+          `Could not find invocation with CID ${task.link().toString()} for receipt with CID: ${receipt.link().toString()}`
+        )
       }
 
       // log any likely JSON serialization errors in the receipt