Edge function written with Oak causes edge runtime container exit 139 on CLI >= 1.108.4 edge runtime >= 1.22.3

[calebdelnay]

Describe the bug
Edge runtime container exits unexpectedly upon HTTP request when edge function uses oak 12.6.1, Supabase CLI >= 1.108.4, Edge Runtime >= 1.22.3.

DEBUG Specifier "https://deno.land/x/oak@v12.6.1/response.ts" was not mapped in import map.
Segmentation fault (core dumped)
2023/11/01 17:31:32 Sent Header: Host [api.moby.localhost]
2023/11/01 17:31:32 Sent Header: User-Agent [Docker-Client/unknown-version (linux)]
2023/11/01 17:31:32 Send Done
2023/11/01 17:31:33 Recv First Byte
error running container: exit 139

Response is:

{
    "message": "An invalid response was received from the upstream server"
}

To Reproduce
With Supabase CLI >= 1.108.4, create a function and use Oak as the HTTP server, per the Supabase guide here:
https://github.com/supabase/supabase/tree/master/examples/edge-functions/supabase/functions/oak-server

Run a request against the function. It'll fail and your terminal for the function will give an exit 139 error.

Expected behavior
Request handled successfully returning the string

This is an example Oak server running on Edge Functions!

[sweatybridge]

Moving this to edge runtime repo since the examples are maintained by @laktek

[github-actions]

🎉 This issue has been resolved in version 1.29.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀