[world-postgres] Add migrations from pg-boss to graphile-worker queue#1126
[world-postgres] Add migrations from pg-boss to graphile-worker queue#1126VaguelySerious merged 11 commits intomainfrom
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: kschmelter13 <kschmelter13@gmail.com>
Signed-off-by: kschmelter13 <kschmelter13@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: kschmelter13 <kschmelter13@gmail.com>
Signed-off-by: kschmelter13 <kschmelter13@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: kschmelter13 <kschmelter13@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Minor to patch Co-authored-by: Peter Wielander <mittgfu@gmail.com> Signed-off-by: Kevin <kschmelter13@gmail.com>
Co-authored-by: Peter Wielander <mittgfu@gmail.com> Signed-off-by: Kevin <kschmelter13@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
|
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests🌍 Community Worlds (46 failed)mongodb (1 failed):
turso (45 failed):
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 🌍 Community Worlds
✅ 📋 Other
|
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express workflow with 1 step💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro workflow with 25 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 50 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Promise.all with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express Promise.race with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express Stream Benchmarks (includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
|
|
@VaguelySerious LGTM! The retry count is independent from workflow's retries, right? So this is not where retry delays, attempt count etc. are persisted, and therefore no need to migrate the |
|
@rovo89 Yes, retry-count is handled in the Step materialization in Storage, and not in the queue. The retry count mentioned in the migration is for queue messages |
Follow-up to #1124 to add migrations for backwards-compat.