Why do you want to contribute?
I recently set up trigger.dev locally and while exploring the codebase, I reproduced issue #4819, where batchTrigger returns a failed run as isCached=true instead of creating a fresh one when the idempotency key isn't cleared after failure.
I confirmed the bug locally by querying the TaskRun table directly - the failed run still has its idempotencyKey attached with a 30 day expiry, and only one always-failing-task run was created despite two batchTrigger calls with the same key 12 seconds apart.
I'd like to contribute a fix for this, and then take on more issues as I get more familiar with the codebase.
Prior contributions or relevant experience
I've contributed to large codebases at my previous company, though they were closed source. This would be my first open source contribution at this scale. I'm comfortable with TypeScript and have spent time understanding the monorepo structure.
Why do you want to contribute?
I recently set up trigger.dev locally and while exploring the codebase, I reproduced issue #4819, where batchTrigger returns a failed run as isCached=true instead of creating a fresh one when the idempotency key isn't cleared after failure.
I confirmed the bug locally by querying the TaskRun table directly - the failed run still has its idempotencyKey attached with a 30 day expiry, and only one always-failing-task run was created despite two batchTrigger calls with the same key 12 seconds apart.
I'd like to contribute a fix for this, and then take on more issues as I get more familiar with the codebase.
Prior contributions or relevant experience
I've contributed to large codebases at my previous company, though they were closed source. This would be my first open source contribution at this scale. I'm comfortable with TypeScript and have spent time understanding the monorepo structure.