Blake Gentry

Search path is currently the only way for the migrator to execute migrations against an alternate schema. I think to do otherwise we would probably need to evolve some sort...

That’s going to be a session level change which persists on the connection even after it’s returned in the database pool, right? My understanding is the only way to reliably...

Seems likely you’re using the dbsql driver? This appears to be a bug with that driver not handling duration types as db interval types correctly.

Hmm, you must have at least gotten a different error when using pgx? The message above is specific to pq which isn’t used at all by the pgx driver.

@brandur hmm, wondering if there still might be a dbsql-specific issue here given that the "fix" was to use the pgx driver 🤔

@varunbpatil yes, PRs welcome. This is something we’ll also want to add test coverage for in the shared driver test suite to make sure it stays working.

This is available in the UI as of riverui [v0.10.0](https://github.com/riverqueue/riverui/releases/tag/v0.10.0). I think the only thing missing is web documentation about the riverlog package and accessing these logs in the UI.

I believe I just encountered this same issue when using `trailingSlash: 'never'`. The regression appears to be introduced as of `@astrojs/vercel` v7.8.2. I have a route served by a rest...

No, my workaround has been to pin the version from before the breakage and hope somebody takes action on this reported issue 😂🤞🏻

For my specific issue, I have narrowed it down to #373 / 5b802a4099743c86418747872171bbe224caaa6d that introduced this breakage (cc @hrabiel). If I use patch-package to apply this diff to revert the...