Matt Aitken
0591db5f2b
* Test for checkpoints * Make sourceTaskAttemptId optional on resumeBatchRun * Removed all completions/executions logic from the shared queue consumer * Removed the sourceTaskAttemptId from ResumeBatchRunService * Revert "Removed all completions/executions logic from the shared queue consumer" This reverts commit d35398d50463c81a1975bb5d5bcfca66a24b8ede. * WIP on triggerAndWait… * Fixed triggerAndWait continuing when a checkpoint completes * Remove the ResumeAttempt code that fails attempts (was protecting against infinite restores) * Removed messageBody.data.completedAttemptIds.length === 0 commented out code * Don’t ack if there’s no batchRun * Added the marqs?.replaceMessage back in but NOT when there’s no checkpoint. More logging This is a fix for when some attempts fail * Improvement to the test task that now randomly fails attempts * When a checkpoint happens, only continue the attempt if it’s in the correct state * Changeset for rollback in branch * Set keepRunAlive to false when the dependent task isn’t finished * Changeset manual version (to get inline with the hotfix branch) * Changeset: Fixes for continuing after waits * Latest lockfile (after manual changeset version)
About Trigger.dev
Trigger.dev is an open source platform and SDK which allows you to create long-running background jobs with no timeouts. Write normal async code, deploy, and never hit a timeout.
Features:
- JavaScript and TypeScript SDK
- Write reliable code by default
- No infrastructure to manage
- Works with your existing tech stack
In your codebase
Create tasks where they belong: in your codebase. Version control, localhost, test and review like you're already used to.
import { task } from "@trigger.dev/sdk/v3";
//1. You need to export each task
export const helloWorld = task({
//2. Use a unique id for each task
id: "hello-world",
//3. The run function is the main function of the task
run: async (payload: { message: string }) => {
//4. You can write code that runs for a long time here, there are no timeouts
console.log(payload.message);
},
});
Deployment
Use our SDK to write tasks in your codebase. There's no infrastructure to manage, your tasks automatically scale and connect to our cloud. Or you can always self-host.
Environments
We support Development, Staging, and Production environments, allowing you to test your tasks before deploying them to production.
Full visibility of every job run
View every task in every run so you can tell exactly what happened. We provide a full trace view of every task run so you can see what happened at every step.
Getting started
Visit our docs here for a full guide on how to get started with Trigger.dev.
Self-host
If you prefer to self-host, you can follow our self-hosting guide.
Development
To setup and develop locally or contribute to the open source project, follow our development guide.