Bug report

Describe the bug

Hey all! I’m building a relatively simple edge function that just takes a request body, validates it, and saves it in the db. and for some reason, I can’t figure out why but I keep getting a 502 response from this endpoint.

I’ve tried deleting and redeploying the function. I’ve tried commenting out most/all of the function but a response in an effort of trying to isolate if it’s a package issue, supabase connection issue, etc… and nothing has worked.

Here’s a codepen with the code for my edge function: https://codesandbox.io/s/strange-wilson-ylnfpp?file=/src/functions/create-event/index.ts

I copied and pasted the example found here: https://github.com/supabase/supabase/blob/master/examples/edge-functions/supabase/functions/select-from-table-with-auth-rls/index.ts and that function is working fine. But for some reason my function is returning the following error:

502: Bad Gateway (ORIGIN_BOOT_RPC_ERROR)
The subhoster origin returned a failure status for the boot RPC call. Status: 500 Internal Server Error

To Reproduce

• Get the code for my edge function in question here: https://codesandbox.io/s/strange-wilson-ylnfpp?file=/src/functions/create-event/index.ts
• Deploy the function to a supabase project (I’m sure the project won’t have an events table, that’s fine. IF an error is returned stating that relating doesn’t exist, then I’d be ecstatic.
• Hit the function with with your favorite api tool.

Expected behavior

In my project, I’d expect the function to take the in the body, validate it, store a new record, and return a non 500 response

System information

• WSL (Ubuntu)
• Version of supabase-js: 1.35.2
• Version of Node.js: 16.13.1