Naser Aleisa

@jacob-8 You can customize your rules like [this](https://github.com/thenbe/sveltekit-eslint-antfu/blob/main/eslint.config.js#L16-L25). Would that work for you? Or have I misunderstood your use case?

The issue is not *immediately* reproducible on a brand new supabase.com project. However, I can still reproduce it shortly thereafter. I can't nail down the exact minimal reproduction yet. One...

I added the minimal reproduction steps to the original post.

It turns out this is solved by waiting a bit after running `supabase db reset --linked`. Perhaps we should log a message to the user when they run that command?...

Were you able to reproduce the issue? I initially thought I was doing something wrong, but it seems this is broken for any project on supabase.com (see minimal repro). I'm...

> Since it's affecting your hosted project, our support team can unblock you if you create a support ticket. It's good to know I can do that, but that would...

You're right, those minimal repro steps do not lead to that error (`absolute path not allowed`) when using the sql console on supabase.com. Afterwards, when I tried to run my...

I managed to reproduce the issue on a VPS and narrow it down to the "mode" `supabase db reset` is executed in. The reset consistently fails in "remote mode", yet...

Here is the output when running with `--debug`. ## output of good command ``` $ sudo /nix/store/wlkinnxalw2zpanc6pw5ym05shpmch8i-supabase-cli-1.183.0/bin/supabase db reset --local --debug Supabase CLI 1.183.0 Resetting local database... 2024/07/08 05:36:44 Sent...

> Might already be fixed (by accident) in the v0.28 branch. I can reproduce the bug on the latest v0.28 branch (points to 5d38c1b52e8f at time of writing).