Deno edge function encounters unexpected bug with supabase-js client in local deployment

Open JungeWerther opened this issue 1 year ago • 3 comments

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Description

I'm able to deploy a deno edge function locally and run a test without problems using supabase functions serve --env-file ./supabase/functions/.env.local. The supabase-js client library loads fine when I run deno test --allow-all ./tests/jl-call-test.ts --env=./functions/.env.local. However, the functions server shuts down with the following error:

Segmentation fault (core dumped)
error running container: exit 139

which happens at

const client = createClient(
      supabaseUrl, 
      supabaseKey, {
        auth: {
          autoRefreshToken: false,
          persistSession: false,
          detectSessionInUrl: false,
        },
        db: {
          schema: 'custom_schema_name'
        }
      })

As I said the above snippet runs perfectly well in my unit test. Running with the --debug flag outputs no extra information.

Weirdly, if I remove the supabase-js client logic, my function is responsive in local development and works as expected. Any idea what might be going on here? Thanks 🫶