From afd27f038e9eebb83e1148000505b451c7e3be50 Mon Sep 17 00:00:00 2001 From: ctrlc03 <93448202+ctrlc03@users.noreply.github.com> Date: Mon, 13 May 2024 09:25:51 +0100 Subject: [PATCH 1/3] fix: increase memory limit of finalizeCeremony CF --- packages/backend/src/functions/ceremony.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/backend/src/functions/ceremony.ts b/packages/backend/src/functions/ceremony.ts index 9bf72df7..2183d3f0 100644 --- a/packages/backend/src/functions/ceremony.ts +++ b/packages/backend/src/functions/ceremony.ts @@ -273,7 +273,7 @@ export const initEmptyWaitingQueueForCircuit = functions export const finalizeCeremony = functions .region("europe-west1") .runWith({ - memory: "512MB" + memory: "1GB" }) .https.onCall(async (data: { ceremonyId: string }, context: functions.https.CallableContext): Promise => { if (!context.auth || !context.auth.token.coordinator) logAndThrowError(COMMON_ERRORS.CM_NOT_COORDINATOR_ROLE) From c0f6a3d12a200fa89867463e73d866e8126a9193 Mon Sep 17 00:00:00 2001 From: Nico Serrano Date: Wed, 12 Jun 2024 15:12:46 -0400 Subject: [PATCH 2/3] feat: reexecute deployment --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b029e520..7f2ea54f 100644 --- a/README.md +++ b/README.md @@ -63,7 +63,7 @@ | p0tion has been intentionally designed as an agnostic-from-ceremony public good toolkit, with the aim of making Groth16 zk-applications scale and become production-ready in a safe and secure manner by running Phase 2 Trusted Setup ceremonies. | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -Our design philosophy ensures that p0tion stands as the optimal choice for running secure Groth16 zk-applications via automated phase2 ceremonies. The entire process has been streamlined through the easy to use and configure infrastructure, simplifying coordination, scalability, and minimizing the burden of conducting ceremonies from scratch. Additionally, our clear and user-friendly documentation and code, as well as rapid onboarding and deployment, guarantee an adaptable tool that can easily accommodate the evolving needs of developers +Our design philosophy ensures that p0tion stands as the optimal choice for running secure Groth16 zk-applications via automated phase2 ceremonies. The entire process has been streamlined through the easy to use and configure infrastructure, simplifying coordination, scalability, and minimizing the burden of conducting ceremonies from scratch. Additionally, our clear and user-friendly documentation and code, as well as rapid onboarding and deployment, guarantee an adaptable tool that can easily accommodate the evolving needs of developers. ## 📦 Packages From 7197129a42806ab323eb56c0d10a0830141b949d Mon Sep 17 00:00:00 2001 From: Jayden Date: Tue, 2 Jul 2024 12:49:03 +0800 Subject: [PATCH 3/3] Fix the issue that 'Firebase Function' might can't deploy MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Might encounter an error when running the following commands: ```shell cd packages/backend yarn firebase:deploy ``` Error message: ``` ⚠ functions: Upload Error: HTTP Error: 400, EntityTooLargeYour proposed upload is larger than the maximum object size specified in your Policy Document.
Content-length exceeds upper bound on range
 ``` Error Details: The uploaded Firebase function source code package is too large (exceeds 100MB). Cause: After running `terraform` in the `backend/aws` folder, temporary files larger than 500MB are generated in `backend/aws`. The `backend/aws` folder is not needed for deploying Firebase functions. **Solution**: Modify the `firebase.json` file to exclude the `backend/aws` folder: Before: ```json "functions": { "predeploy": "yarn --cwd \"$RESOURCE_DIR\" build", "source": "." } ``` After modification: ```json "functions": { "predeploy": "yarn --cwd \"$RESOURCE_DIR\" build", "source": ".", "ignore": [ "node_modules", "aws" ] } ``` - Note: - Why add `node_modules`? In the [firebase-tools source code](https://github.com/firebase/firebase-tools/blob/v13.12.0/src/deploy/functions/prepareFunctionsUpload.ts#L75): ```typescript const ignore = config.ignore || ["node_modules", ".git"]; ``` When the `ignore` node is not configured, `node_modules` is automatically ignored. However, when `ignore` is manually added, you must also manually add `node_modules` to the `ignore` list. --- packages/backend/firebase.json | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/packages/backend/firebase.json b/packages/backend/firebase.json index 0eb7cc33..1be93274 100644 --- a/packages/backend/firebase.json +++ b/packages/backend/firebase.json @@ -5,7 +5,11 @@ }, "functions": { "predeploy": "yarn --cwd \"$RESOURCE_DIR\" build", - "source": "." + "source": ".", + "ignore": [ + "node_modules", + "aws" + ] }, "emulators": { "singleProjectMode": true,