Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Create file 'supabase/tests/init-function.sql' with content
CREATE
OR REPLACE FUNCTION public.test () RETURNS integerAS $$
BEGIN
return 1;
END;
$$ LANGUAGE plpgsql;
- Create file 'supabase/tests/test-sample.sql' with content
BEGIN;
\i init-function.sql
SELECT plan(1);
SELECT ok( 1=1, 'Oups 1!=1');
SELECT * FROM finish();
ROLLBACK;
- run
supabase db test "supabase/tests/test-sample.sql"See error:
psql:XXXXX/tests/test-sample.sql:5: error: init-function.sql: No such file or directory
Expected behavior
We should have the relative import correctly imported
System information
Rerun the failing command with --create-ticket flag.
- Version of OS: Mac OS
- Version of CLI: v2.72.1
- Version of Docker: 29.1.5
- Versions of services:
SERVICE IMAGE | LOCAL | LINKED
------------------------|------------------------|------------
supabase/postgres | 17.4.1.043 | 17.4.1.043
supabase/gotrue | v2.179.0 | v2.185.0
postgrest/postgrest | v12.2.3 | v12.2.3
supabase/realtime | v2.69.2 | -
supabase/storage-api | v1.33.5 | v1.33.0
supabase/edge-runtime | v1.68.4 | -
supabase/studio | 2026.01.12-sha-4e9b718 | -
supabase/postgres-meta | v0.95.2 | -
supabase/logflare | 1.28.0 | -
supabase/supavisor | 2.7.4 | -
Additional context
Seems that the bug was introduced by:
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
supabase db test "supabase/tests/test-sample.sql"See error:Expected behavior
We should have the relative import correctly imported
System information
Rerun the failing command with
--create-ticketflag.SERVICE IMAGE | LOCAL | LINKED
------------------------|------------------------|------------
supabase/postgres | 17.4.1.043 | 17.4.1.043
supabase/gotrue | v2.179.0 | v2.185.0
postgrest/postgrest | v12.2.3 | v12.2.3
supabase/realtime | v2.69.2 | -
supabase/storage-api | v1.33.5 | v1.33.0
supabase/edge-runtime | v1.68.4 | -
supabase/studio | 2026.01.12-sha-4e9b718 | -
supabase/postgres-meta | v0.95.2 | -
supabase/logflare | 1.28.0 | -
supabase/supavisor | 2.7.4 | -
Additional context
Seems that the bug was introduced by:
supabase test dbwhen usingdocker-outside-of-docker#4523