-
Notifications
You must be signed in to change notification settings - Fork 1
Remaining Issues to Address
When we receive increased traffic to the site, the site ends up crashing with OSError: Too Many Open Files. This is an issue not with our end, but rather an issue with an Mangum, an adapter for running ASGI (e.g. FastAPI) applications in AWS Lambda.
Redeploying the current deployment resolves the issue temporarily, so as a workaround, we deploy an AWS Lambda function to automatically trigger a redeploy upon seeing an error in our Axiom logs.
Some possible remedies for this are:
- Migrating the backend to AWS Lambda
- Migrating the backend to a cloud server (instead of serverless)
- Migrating the backend to TypeScript, allowing easier integration with Next.js
Update: The exception trace traces back to the file vc_init.py, which was recently updated to support later versions of Python. This may resolve the above issue.
This year, we used a barcode scanner to scan barcodes on participants' badges to check them into the hackathon and its workshops. However, on certain devices, especially iPhones, the scanner generally failed to detect barcodes, forcing us to type the numbers of the barcode in manually. This may have been due to the focusing ability of the cameras.
On some devices, the fireflies on the home page cause CPU usage to spike. See #192 for a more in-depth explanation of the issue.
When building the frontend application, multiple errors about dynamic server usage appear because Next.js attempts to build pages statically. See #168 for a more in-depth explanation of the issue.