@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?
@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?
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!
@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)!
@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
@rauchg@WebReflection@tomasz_ducin It's semantically equivalent to await new Promise((resolve, reject) => { .. }), where the handler is invoked immediately.