Seeding buckets rate limit ? #3939
Description
Describe the bug
I'm trying to seed the buckets in my Supabase project using the command supabase seed buckets --linked. I initially intended to upload around 1000 images, but after ~200 uploads, I consistently get the following error:
failed to execute http request: Post "https://aixeqyjjwvhcqgvbphva.supabase.co/storage/v1/object/users_avatars/avatar_9328091a-a5a7-4596-88c3-9da3cb84fa57.jpg": http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown GOAWAY] after Request.Body was written; define Request.GetBody to avoid this error
The seeding stops at roughly the 200-image mark (i tried several times). This makes me think I’m hitting a rate limit, especially since the command sends an HTTP request for each image, which seems excessive.
To Reproduce
Create a bucket and attempt to upload more than 300 images using supabase seed buckets --linked.
Expected behavior
I would expect the seeding to complete successfully regardless of the number of images—unless hitting another limit. Additionally, using a separate HTTP request for each image seems inefficient. A streaming socket or a single batch upload (e.g. zipped content) would be better.
Screenshots
System information
- Ticket ID: af1bf8cd048244c48940f1e8d67d84e7
- Version of OS: Windows 11 Pro 24H2, build 26100.4652
- Version of CLI: 2.33.5
- Version of Docker: 28.0.1, build 068a01e
- Versions of services:
| SERVICE IMAGE | LOCAL | LINKED |
|---|---|---|
| supabase/postgres | 17.4.1.054 | 17.4.1.054 |
| supabase/gotrue | v2.177.0 | v2.177.0 |
| postgrest/postgrest | v12.2.12 | - |
| supabase/realtime | v2.41.9 | - |
| supabase/storage-api | v1.25.12 | - |
| supabase/edge-runtime | v1.68.2 | - |
| supabase/studio | 2025.07.28-sha-578b707 | - |
| supabase/postgres-meta | v0.91.3 | - |
| supabase/logflare | 1.14.2 | - |
| supabase/supavisor | 2.5.7 | - |