[Bug]: runtime error: slice bounds out of range [1:0]

[wwjCMP]

What happened?

supabase migration up

When i want to update quivr, this issue appear.

runtime error: slice bounds out of range [1:0]

Relevant log output

I:\Softwares\quivr>supabase migration up --debug
Supabase CLI 1.165.0
Connecting to local database...
2024/05/14 22:42:20 Connect Start: tcp 127.0.0.1:54322
2024/05/14 22:42:20 Connect Done: tcp 127.0.0.1:54322
2024/05/14 22:42:20 PG Send: {"Type":"StartupMessage","ProtocolVersion":196608,"Parameters":{"database":"postgres","user":"postgres"}}
2024/05/14 22:42:20 PG Recv: {"Type":"AuthenticationSASL","AuthMechanisms":["SCRAM-SHA-256"]}
2024/05/14 22:42:20 PG Send: {"Type":"SASLInitialResponse","AuthMechanism":"SCRAM-SHA-256","Data":"n,,n=,r=ckL5udOw9kPm9/zf9Rtnkp3f"}
2024/05/14 22:42:20 PG Recv: {"Type":"AuthenticationSASLContinue","Data":"r=ckL5udOw9kPm9/zf9Rtnkp3fUNiNSE8U+lFspBpmFSWl9e1M,s=etvmQoaDRo8VEXbHxLk7fQ==,i=4096"}
2024/05/14 22:42:20 PG Send: {"Type":"SASLResponse","Data":"c=biws,r=ckL5udOw9kPm9/zf9Rtnkp3fUNiNSE8U+lFspBpmFSWl9e1M,p=e7NMJ+h/Xj/lWnsurqrY7jST0XGpsZ8T6vartdNJxLI="}
2024/05/14 22:42:20 PG Recv: {"Type":"AuthenticationSASLFinal","Data":"v=n+wCQBFFggAJ37Sd3/q3ZMCrg7GKd3bTpr+5FhDgE3Y="}
2024/05/14 22:42:20 PG Recv: {"Type":"AuthenticationOK"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"application_name","Value":""}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"client_encoding","Value":"UTF8"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"DateStyle","Value":"ISO, MDY"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"default_transaction_read_only","Value":"off"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"in_hot_standby","Value":"off"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"integer_datetimes","Value":"on"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"IntervalStyle","Value":"postgres"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"is_superuser","Value":"off"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"server_encoding","Value":"UTF8"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"server_version","Value":"15.1 (Ubuntu 15.1-1.pgdg20.04+1)"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"session_authorization","Value":"postgres"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"standard_conforming_strings","Value":"on"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterStatus","Name":"TimeZone","Value":"UTC"}
2024/05/14 22:42:20 PG Recv: {"Type":"BackendKeyData","ProcessID":216,"SecretKey":3263032831}
2024/05/14 22:42:20 PG Recv: {"Type":"ReadyForQuery","TxStatus":"I"}
2024/05/14 22:42:20 PG Send: {"Type":"Parse","Name":"lrupsc_1_0","Query":"SELECT version FROM supabase_migrations.schema_migrations ORDER BY version","ParameterOIDs":null}
2024/05/14 22:42:20 PG Send: {"Type":"Describe","ObjectType":"S","Name":"lrupsc_1_0"}
2024/05/14 22:42:20 PG Send: {"Type":"Sync"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParseComplete"}
2024/05/14 22:42:20 PG Recv: {"Type":"ParameterDescription","ParameterOIDs":[]}
2024/05/14 22:42:20 PG Recv: {"Type":"RowDescription","Fields":[{"Name":"version","TableOID":17609,"TableAttributeNumber":1,"DataTypeOID":25,"DataTypeSize":-1,"TypeModifier":-1,"Format":0}]}
2024/05/14 22:42:20 PG Recv: {"Type":"ReadyForQuery","TxStatus":"I"}
2024/05/14 22:42:20 PG Send: {"Type":"Bind","DestinationPortal":"","PreparedStatement":"lrupsc_1_0","ParameterFormatCodes":null,"Parameters":[],"ResultFormatCodes":[0]}
2024/05/14 22:42:20 PG Send: {"Type":"Describe","ObjectType":"P","Name":""}
2024/05/14 22:42:20 PG Send: {"Type":"Execute","Portal":"","MaxRows":0}
2024/05/14 22:42:20 PG Send: {"Type":"Sync"}
2024/05/14 22:42:20 PG Recv: {"Type":"BindComplete"}
2024/05/14 22:42:20 PG Recv: {"Type":"RowDescription","Fields":[{"Name":"version","TableOID":17609,"TableAttributeNumber":1,"DataTypeOID":25,"DataTypeSize":-1,"TypeModifier":-1,"Format":0}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240103173626"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240103175048"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240103181249"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240103181925"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240103193921"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240103194255"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240103204741"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240103231656"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240103234423"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240107231636"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240119070124"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240119222036"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240120004107"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240121195523"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240122194117"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240125230346"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240206040636"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240207034043"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240207071108"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240216192826"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240228182948"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240304223646"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240305225452"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240306013910"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240306205133"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240313024244"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240314005817"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240316195514"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240318024425"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240320215813"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240329212126"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240330233534"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240402005455"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240402013303"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240402015128"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240410112108"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240501180719"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"DataRow","Values":[{"text":"20240506150059"}]}
2024/05/14 22:42:20 PG Recv: {"Type":"CommandComplete","CommandTag":"SELECT 38"}
2024/05/14 22:42:20 PG Recv: {"Type":"ReadyForQuery","TxStatus":"I"}
runtime error: slice bounds out of range [1:0]

Twitter / LinkedIn details

No response

[dosubot]

The error "runtime error: slice bounds out of range [1:0]" you're encountering with the Supabase CLI during migration is indicative of an issue where the CLI attempts to access a part of an array or slice that doesn't exist. This can happen for several reasons, such as malformed SQL in your migration files or a bug within the CLI itself.

To address this issue:

1. Ensure Migration File Syntax is Correct: Double-check the SQL syntax in your migration files for any errors or typos.
2. Update Supabase CLI: Run supabase update to ensure you're using the latest version of the CLI, as the issue might have been fixed in a newer release.
3. Split Large Migration Files: If your migration files are large, try splitting them into smaller, more manageable pieces.
4. Review CLI Debug Output: Look for specific error messages in the debug output that might point to the problematic part of your migration file.

These steps should help you identify and resolve the issue causing the runtime error during migration.

Details

Sources

• backend/supabase/migrations/20240103173626_init.sql
• backend/supabase/seed.sql
• backend/supabase/migrations/20240107231636_policies.sql
• docs/configuring/supabase-setup.mdx
• backend/ci-migration.sh
• .env.example
• backend/supabase/config.toml

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.