Joe Haddad

infra @vercel

[Joe Haddad @timer150]

@consolelogwill @rauchg @CaseyGowrie You could leverage Queues to roll resumable streams, a few of our internal demos actually do this.

Have you seen https://t.co/38iOss2Nhf?

[Joe Haddad @timer150]

@neoromantic @rauchg @CaseyGowrie We are going to continue investment into the Workflow SDK!

cc @pranaygp

[Joe Haddad @timer150]

@tobiastornros @rauchg @CaseyGowrie Yes! You can o11y in your project's o11y tab. We'll update the docs for this!

[Joe Haddad @timer150]

@marclou @rauchg Let us know what we can improve! Looking forward to feedback 😁

[Joe Haddad @timer150]

@BenjDicken @rauchg It is hard for me to imagine maintaining Vercel’s DX for arbitrary compute where we do not have an event binding interface. What does this look like to you? 👀

Have you looked at Sandbox for your use case? Can you share the specific type of work you want to do in this VPS?

[Joe Haddad @timer150]

Is indefinitely actually desirable here?

For long running tasks, we typically see someone implement checkpointing so that a transient failure (e.g. upstream API) does not cause you to lose all progress.

This can generalize to Queues or Workflow where a task might take 8 hours, but you carve it up into 10 minute chunks.

I would love to learn more specifics!

[Joe Haddad @timer150]

@k_firsov @cramforce @rauchg Mind sharing more details (here or in DM)?

[Joe Haddad @timer150]

@maxleiter Do you have thoughts on https://t.co/OxxSyLdGnH?

[Joe Haddad @timer150]

@mxkaske Sent you a PR to replace your middleware with routes instead! This will guarantee your site is always fast https://t.co/W9vkAyObcF

[Joe Haddad @timer150]

@karthikkalyan90 very aligned- nothing’s worse than a ton of nits!

[Joe Haddad @timer150]

I would switch to a new AI code review tool tomorrow if it _______.

We'll build the best ideas and give you early access!

[Joe Haddad @timer150]

@huozhi I can imagine many layers to this, for starters the bot should auto resolve comments it previously found and are now fixed.

Automated approvals sound great if it can follow a repo policy (only for docs, bug fixes that do not introduce new features, etc)!

[Joe Haddad @timer150]

@hp_arora 🎙️ we're waiting

[Joe Haddad @timer150]

@dobroslav_dev @vercel_changes @elysiaJS @anthonysheww think we can get this working? We have our bun builder that could be used automatically: https://t.co/i1l3YFmMz2

[Joe Haddad @timer150]

@preetsuthar17 @vercel what is the first feature you’d ship?

[Joe Haddad @timer150]

@ScriptedAlchemy @rauchg @kdy1dev @tomlienard Real Rust with Active CPU pricing.

https://t.co/UoByYaNi5s

[Joe Haddad @timer150]

@Tofugrass @vercel_changes All plans, including Hobby (free)

[Joe Haddad @timer150]

@WebReflection @rauchg @tomasz_ducin @WebReflection I think we're talking past one another - the receive handler in initial tweet handles the entire lifecycle of message handling.

Without a callback, you'd need:
const { message, ack, reject, extend } = await receive("topic", "consumer");

https://t.co/awlrtd8ioM

[Joe Haddad @timer150]

@WebReflection @rauchg @tomasz_ducin send() resolves once the message is durably persisted to the queue, before processing starts.

[Joe Haddad @timer150]

@rauchg @WebReflection @tomasz_ducin @WebReflection given this insight, how would you design the API to receive and process a single message? 👀

[Joe Haddad @timer150]

@rauchg @WebReflection @tomasz_ducin It's semantically equivalent to await new Promise((resolve, reject) => { .. }), where the handler is invoked immediately.