You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Release 1.202.4 and later break seed on reset - Windows #2734
Describe the bug
Since Release 1.202.4, db reset no longer recognises my seed.sql file even though it exists in the expected location, supabase/seed.sql
To Reproduce
Steps to reproduce the behavior:
Update to supabase cli v1.202.4 or later
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
$ npx supabase@beta db reset
Need to install the following packages:
supabase@1.204.3
Ok to proceed? (y) y
Resetting local database...
Recreating database...
Setting up initial schema...
Seeding globals from roles.sql...
Applying migration ....
Seeding data from supabase/seed.sql...
Restarting containers...
@sweatybridge To clarify, my seed file does exist at that location but I still get the warning message that it doesn't exist. This was fixed on db reset but doesn't appear to have been a universal fix.
The new config settings are not set in my config as they're quite recent. In that case I would expect the default behaviour be that the seed is not performed after a migration as this is the precedent behaviour, in which case there would be no need to check for the seed file.
@sweatybridge See the original bug at the top here. db reset was fixed i.e. the No seed file matched pattern warning no longer shows with the db reset command. It was an issue with reading the file system correctly on windows I believe. However, I'm still seeing the warning when using db push and db pull
Activity
sweatybridge commentedon Oct 8, 2024
This is due to a bug in path separator handling. Could you try the beta release?
DuncanLHS commentedon Oct 9, 2024
@sweatybridge That's fixed it. Thanks.
DuncanLHS commentedon Oct 24, 2024
Still seeing this issue on db pull and push:
Not sure why as I don't believe the seed is used in these commands.
sweatybridge commentedon Oct 24, 2024
Hi @DuncanLHS, this is due to a recent change we made that validates config.toml more rigorously.
You can avoid this log message by updating config.toml to disable seed config.
DuncanLHS commentedon Oct 24, 2024
@sweatybridge To clarify, my seed file does exist at that location but I still get the warning message that it doesn't exist. This was fixed on db reset but doesn't appear to have been a universal fix.
The new config settings are not set in my config as they're quite recent. In that case I would expect the default behaviour be that the seed is not performed after a migration as this is the precedent behaviour, in which case there would be no need to check for the seed file.
sweatybridge commentedon Oct 24, 2024
We parse and validate all config at the start of the command, even if some parts of it are not used.
This is weird because reset shouldn't fix anything as the error is from config validation. Which directory are you running supabase commands from?
DuncanLHS commentedon Oct 25, 2024
@sweatybridge See the original bug at the top here.
db resetwas fixed i.e. theNo seed file matched patternwarning no longer shows with thedb resetcommand. It was an issue with reading the file system correctly on windows I believe. However, I'm still seeing the warning when usingdb pushanddb pull