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 — Reapply "Refactor the Celery Beat integration (#3105)" (#3144) by antonpirker · Pull Request #3175 · getsentry/sentry-python Conversation
Contributor
This reverts commit d818e8f. This reverts the revert that was done to mitigate the regression error with Crons not being sending ok/error checkins. We have a fix ready in #3155 that fixes that regression that will be merge into this PR. General NotesThank you for contributing to Please add tests to validate your changes, and lint your code using Running the test suite on your PR might require maintainer approval. Some tests (AWS Lambda) additionally require a maintainer to add a special label to run and will fail if the label is not present. For maintainersSensitive test suites require maintainer review to ensure that tests do not compromise our secrets. This review must be repeated after any code revisions. Before running sensitive test suites, please carefully check the PR. Then, apply the
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
sentrivana
approved these changes
#3176) After refactoring the Celery Beat integration there was a regression, where the ok/error check ins for crons where not sent. This fixes the problem and adds integrations tests to not have this regression again.
antonpirker
enabled auto-merge (squash)
sentrivana
pushed a commit
that referenced
this pull request
This reverts the revert that was done to mitigate the regression error with Crons not being sending ok/error checkins. This reapplies the refactoring and also fixes the root cause of the regression and also adds integration tests to make sure it does not happen again.
arjennienhuis
pushed a commit
to arjennienhuis/sentry-python
that referenced
this pull request
…entry#3144) (getsentry#3175) This reverts the revert that was done to mitigate the regression error with Crons not being sending ok/error checkins. This reapplies the refactoring and also fixes the root cause of the regression and also adds integration tests to make sure it does not happen again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ReviewersUh oh!
There was an error while loading. Please reload this page. AssigneesLabels
Component: SDK Core
ProjectsMilestoneNo milestoneDevelopmentSuccessfully merging this pull request may close these issues. Uh oh!
There was an error while loading. Please reload this page. 2 participantsAdd 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. |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |