Conversation
jjnesbitt
commented
Dec 19, 2025
jjnesbitt
commented
Dec 19, 2025
e1778c0 to
0fd1bd5
Compare
The `yaml.safe_load` function is much slower
12c2650 to
567f361
Compare
567f361 to
de82b48
Compare
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.
Adapted from @mvandenburgh's initial work.
There was a previous iteration that used the
web_hook_logstable. As far as I can tell, that table has been done away with, in favor of aweb_hook_logs_dailytable, which is somewhat ephemeral. So, we are forced to resort back to constructing the webhook from the underlying db data.There are other miscellaneous fixes included, which would prevent the backfill script from properly running. These include adding the
dotenvjob type, and using a different yaml loader (yaml.safe_loadis very slow).