Repository navigation
Conversation
`graphileWorkerIntegration({ monitorCronJobs: true })` sends check-ins for
the jobs the graphile-worker crontab schedules, using the crontab item
identifier as monitor slug. `excludeCronJobs` skips items.
Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
size-limit report 📦Compared: 1a3c209 (PR test merge using develop at e1ec28b) Against: e1ec28b (develop) · base run #64891 ✅ Baseline matches: this diff contains only this PR's changes.
|
Bun's `bun run` doesn't inject the channels, and the CJS test of the ESM-only graphile-worker 0.18 isn't hooked on Node 20 or Deno. Co-Authored-By: Claude <noreply@anthropic.com>
1 of 3 tasks
Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
Optional E2E testsSome optional checks were not successful. They do not block the merge. 4 not successful, 49 successful. See the run.
Successful checks
|
…er-crons # Conflicts: # dev-packages/bun-integration-tests/node-suites/excludes.ts # packages/aws-serverless/src/index.ts # packages/bun/src/index.ts # packages/elysia/src/index.ts # packages/google-cloud-serverless/src/index.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of a series adding automatic Crons monitoring for the most-used job schedulers in each SDK. Check-ins for a monitor that doesn't exist yet are dropped, so today each monitor has to be created by hand with its schedule copied from the code. Sending the job's schedule as the monitor config lets Sentry create the monitor and keep it in sync.
This adds
graphileWorkerIntegrationfor graphile-worker 0.16 to 0.18. WithmonitorCronJobs: true, each job the crontab schedules sendsin_progressandokorerrorcheck-ins, and failures are captured as errors. The slug is the crontab item's identifier (?id=, or the task name). It needs the Sentry runtime hook or bundler plugin, and only a process that runs the crontab sends check-ins.Check-ins go out without a monitor config here. #25476 adds the crontab schedule.