Skip to content

docs(service-job): re-anchor the dead tracker citation to the commit that decided it #20866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
objectstack-fleet merged 1 commit into from
Sep 30, 2026
+2 −2
Merged

docs(service-job): re-anchor the dead tracker citation to the commit that decided it #20866

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/services/service-job/src/db-job-adapter.timeout.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ function makeFakeEngine() {

/**
* The inert cron fixture, now shared with the sibling job suites rather than
* spelled a second time here (#8628, #8748): why February 30th, and why
* spelled a second time here (#8628, commit 226cb71d5): why February 30th, and why
* `'0 0 29 2 *'` is NOT a substitute, live in `never-fires.fixture.ts`.
*
* Nothing here depends on the registration being schedulable: `trigger()`
Expand Down
2 changes: 1 addition & 1 deletion packages/services/service-job/src/never-fires.fixture.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ import type { CronJobAdapter } from './cron-job-adapter.js';
* explicit `trigger()`, a second execution landed, and CI reddened on a package
* the offending PR had usually not touched.
*
* Measured (#8748) by faking ONLY `Date` — real timers, croner's real
* Measured (commit 226cb71d5) by faking ONLY `Date` — real timers, croner's real
* scheduling path — with the registration placed 2/5/10/15 ms before the
* expression's own instant. Under the firing spellings each case gained
* exactly one extra handler run: `records executions` went 1 → 2 execution
Expand Down
Loading