-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.
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
feat: Use a background task to set batch export status to running #23136
Merged
tomasfarias
merged 18 commits into
master
from
feat/use-background-task-to-set-batch-export-to-running
Jun 28, 2024
Merged
feat: Use a background task to set batch export status to running #23136
tomasfarias
merged 18 commits into
master
from
feat/use-background-task-to-set-batch-export-to-running
Jun 28, 2024
Conversation
This file contains 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
The large diff lines are just the nesting being removed, actual changes are small! |
tomasfarias
force-pushed
the
feat/use-background-task-to-set-batch-export-to-running
branch
from
June 21, 2024 12:23
62f95a8
to
4ec5623
Compare
Gilbert09
approved these changes
Jun 21, 2024
tomasfarias
force-pushed
the
feat/use-background-task-to-set-batch-export-to-running
branch
2 times, most recently
from
June 25, 2024 09:02
aed05e0
to
9034a2c
Compare
tomasfarias
changed the base branch from
master
to
feat/person-batch-exports-big-query
June 26, 2024 15:03
tomasfarias
force-pushed
the
feat/use-background-task-to-set-batch-export-to-running
branch
2 times, most recently
from
June 27, 2024 13:46
aef5969
to
1285e61
Compare
This allows us to run the task concurrently instead of timing out on it. It also has the additional benefit of removing a lot of nesting levels!
tomasfarias
force-pushed
the
feat/use-background-task-to-set-batch-export-to-running
branch
from
June 28, 2024 08:09
230bb29
to
c10ff4d
Compare
tomasfarias
deleted the
feat/use-background-task-to-set-batch-export-to-running
branch
June 28, 2024 11:41
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Phanatic
pushed a commit
that referenced
this pull request
Jul 8, 2024
…3136) * feat: Use a background task to set batch export status to running This allows us to run the task concurrently instead of timing out on it. It also has the additional benefit of removing a lot of nesting levels! * fix: Type hints and early return * fix: Update type hint * fix: Merge conflicts * fix: Rebase * fix: Bunch of merge conflicts * Update query snapshots * test: Add unit test * Update query snapshots * chore: Rename file * fix: Use new 3.11 alias * Update query snapshots * Update query snapshots * Update query snapshots * Update query snapshots * Update query snapshots * fix: Use new 3.11 alias * Update query snapshots --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
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.
Problem
We are not reliably setting the status of a batch export run to running. We timeout regularly while waiting for it to be done.
Changes
This allows us to run the task concurrently instead of timing out on it. It also has the additional benefit of removing a lot of nesting levels!
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
Does this work well for both Cloud and self-hosted?
How did you test this code?
Added unit test.