Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Migrations diverge from the applied Supabase migrations starting at 0040_

Abierto
#324 0 comentarios 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
docker, postgresql, typescript

Línea de trabajo

Comienza comparando las migraciones SQL del repositorio desde 0040_ en adelante con la lista de migraciones aplicadas por Supabase incluida en el issue, usando la configuración de Docker para reproducir el esquema. Comprueba la nomenclatura de las columnas de plans, especialmente last_synced_at frente a _last_synced_at, y rastrea el error de tiempo de ejecución informado. Se considera terminado cuando se haya identificado el conjunto de migraciones autoritativo y el esquema local de Docker coincida con el esquema aplicado por Supabase, o cuando se haya documentado la discrepancia restante.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hi everyone,

I’ve run into a significant issue when trying to run the Stripe Sync Engine locally using the Docker setup from this repository.

There appears to be a migration drift between the SQL migrations in this repo and the migrations that Supabase actually applies when installing the Sync Engine. The divergence seems to start around migration 0040_.

Because of this drift, the schema produced by the Docker container does not match the schema that exists on a real Supabase project. A concrete example:

  • Production (Supabase‑applied migrations): column _last_synced_at
  • Local (repo migrations via Docker): column last_synced_at

This leads to runtime errors when testing locally. For example:

error: column "last_synced_at" of relation "plans" does not exist

It would be very helpful to clarify:

  • Which migration set is authoritative: The one in this repo or the one Supabase applies?
  • Whether the drift is intentional or accidental.
  • Whether updated migrations will be published so local development matches production again.

Here the list of the applied migrations that seems missing here:

☑️{"id":38,"name":"active_entitlement","hash":"5b3858e7a52212b01e7f338cf08e29767ab362af","executed_at":"2026-01-12 15:21:19.466032"},
☑️{"id":39,"name":"add_paused_to_subscription_status","hash":"09012b5d128f6ba25b0c8f69a1203546cf1c9f10","executed_at":"2026-01-12 15:21:19.501946"},
{"id":40,"name":"managed_webhooks","hash":"1d453dfd0e27ff0c2de97955c4ec03919af0af7f","executed_at":"2026-01-12 15:21:19.534942"},
{"id":41,"name":"rename_managed_webhooks","hash":"ad7cd1e4971a50790bf997cd157f3403d294484f","executed_at":"2026-01-12 15:21:19.571092"},
{"id":42,"name":"convert_to_jsonb_generated_columns","hash":"e0703a0e5cd9d97db53d773ada1983553e37813c","executed_at":"2026-01-12 15:21:19.604092"},
{"id":43,"name":"add_account_id","hash":"9a6beffdd0972e3657b7118b2c5001be1f815faf","executed_at":"2026-01-12 15:21:24.626232"},
{"id":44,"name":"make_account_id_required","hash":"05c1e9145220e905e0c1ca5329851acaf7e9e506","executed_at":"2026-01-12 15:21:25.195055"},
{"id":45,"name":"sync_status","hash":"2f88c4883fa885a6eaa23b8b02da958ca77a1c21","executed_at":"2026-01-12 15:21:25.29217"},
{"id":46,"name":"sync_status_per_account","hash":"b1f1f3d4fdb4b4cf4e489d4b195c7f0f97f9f27c","executed_at":"2026-01-12 15:21:25.356226"},
{"id":47,"name":"api_key_hashes","hash":"8046e4c57544b8eae277b057d201a28a4529ffe3","executed_at":"2026-01-12 15:21:25.43967"},
{"id":48,"name":"rename_reserved_columns","hash":"e32290f655550ed308a7f2dcb5b0114e49a0558e","executed_at":"2026-01-12 15:21:25.474394"},
{"id":49,"name":"remove_redundant_underscores_from_metadata_tables","hash":"96d6f3a54e17d8e19abd022a030a95a6161bf73e","executed_at":"2026-01-12 15:21:31.216978"},
{"id":50,"name":"rename_id_to_match_stripe_api","hash":"c5300c5a10081c033dab9961f4e3cd6a2440c2b6","executed_at":"2026-01-12 15:21:31.68791"},
{"id":51,"name":"remove_webhook_uuid","hash":"289bee08167858dbf4d04ca184f42681660ebb66","executed_at":"2026-01-12 15:21:33.483772"},
{"id":52,"name":"webhook_url_uniqueness","hash":"d02aec1815ce3a108b8a1def1ff24e865b26db70","executed_at":"2026-01-12 15:21:33.519412"},
{"id":53,"name":"sync_observability","hash":"b79c8d39f1a974a397137d0f9da60c05152aebcd","executed_at":"2026-01-12 15:21:33.55289"},
{"id":54,"name":"drop_sync_status","hash":"3b26ec0eb999f689a37fcb2ccb8b2961b70e74f5","executed_at":"2026-01-12 15:21:33.60815"},
{"id":55,"name":"bigint_money_columns","hash":"2bdd5ebdc6d2d20bb6651fdaf46bcbb8b7c3d345","executed_at":"2026-01-12 15:21:33.643009"},
{"id":56,"name":"sync_run_closed_at","hash":"cdce1986b04e486297b33f13c5c6cb9541faf179","executed_at":"2026-01-12 15:21:33.925093"},
{"id":57,"name":"rename_sync_tables","hash":"8b6975305430e81fd8dfd0045c6b02927332fe37","executed_at":"2026-01-12 15:21:33.964907"},
{"id":58,"name":"improve_sync_runs_status","hash":"aa71a10e66cfaba7d14c3a3d5efea3eecaf381fd","executed_at":"2026-01-12 15:21:34.004982"},
{"id":59,"name":"sigma_subscription_item_change_events_v2_beta","hash":"2bdf8b33664d1aec6f5868616b50f63d67346049","executed_at":"2026-01-12 15:21:34.042477"},
{"id":60,"name":"sigma_exchange_rates_from_usd","hash":"90a5994688f6800e6a3cfc47f6a504889937b833","executed_at":"2026-01-12 15:21:34.100217"}
Lenguaje dominante
TypeScript
Estrellas
1.1k
Forks
118
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de stripe/sync-engine

Todos los issues de stripe/sync-engine

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.