GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||
GeezerVison is showing github.com — feat(rq): Add an option to monitor rq-scheduler jobs by wedamija · Pull Request #8053 · getsentry/sentry-python Conversation
|
Coverage Results 📊✅ 134037 passed | ⏭️ 7317 skipped | Total: 141354 | Pass Rate: 94.82% | Execution Time: 441m 7s 📊 Comparison with Base Branch
➖ Removed Tests (58)View removed tests
All tests are passing successfully. ✅ Patch coverage is 98.96% (95 of 96 changed executable lines covered; target 80%). Changed files with executable lines (2)
Coverage diff@@ Coverage Diff @@ ## master #8053 +/-## ========================================== + Coverage 90.26% 90.27% +0.01% ========================================== Files 202 203 +1 Tracked lines 26660 26813 +153 Branches 9926 10008 +82 ========================================== + Hits 24062 24204 +142 - Misses 2598 2609 +11 - Partials 1510 1515 +5 Generated by Coverage Action |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-Authored-By: Claude <[email protected]>
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Ty, left a few comments 🙏🏻
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
rq-scheduler's crontab parser and Sentry disagree on `n/step` in day of week, single-value ranges like `0-0` and wrapping ranges like `5-1` (which Sentry rejects). Those jobs now check in without a config. Also move the interval conversion to `sentry_sdk/crons/utils.py` (same helper as the APScheduler integration), drop the warning for jobs without an `id`, inline the closing check-in and move the module constants up. Co-Authored-By: Claude <[email protected]>
There was an error while loading. Please reload this page.
Match the Celery beat integration: skip jobs whose schedule can't be expressed as a Sentry Crons monitor config instead of sending check-ins without one. Also close the in_progress check-in with an error if perform_job raises. Co-Authored-By: Claude <[email protected]>
There was an error while loading. Please reload this page.
Close the check-in in a finally block instead of a helper, and keep the job body in place. Co-Authored-By: Claude <[email protected]>
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
🙏🏻
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
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 is a quick fix to keep the arq integration behaviour in line with how other integrations work. Sorry for the churn! Follow-up to #8051. Cron jobs whose schedule Crons can't express are no longer monitored, instead of checking in without a config. This matches Celery beat, and the Huey and RQ integrations from #8052 and #8053. Docs: getsentry/sentry-docs#20056 Co-authored-by: Claude <[email protected]>
## DESCRIBE YOUR PR Adds an RQ section to the Python Crons setup page: turning on `monitor_cron_jobs` for rq-scheduler jobs, how the slug is picked, and which jobs are monitored. SDK PR: getsentry/sentry-python#8053 Stacked on #20057. Merge after the SDK release that includes it. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ --------- Co-authored-by: Claude <[email protected]> Co-authored-by: Ivana Kellyer <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.