refactor: dbnomics#216
Open
nikbpetrov wants to merge 1 commit into
Open
Conversation
Collaborator
Author
|
Tests pass w/ perfect parity. |
Collaborator
Author
|
Tests pass again (old/new matches perfectly), though with predictable differences to prod: there was one more observation published between 00:08:50 when the prod snapshot happened vs when the tests ran today (10ish hours later) |
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
1 participant
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.
both fetch and update jobs do the sinful df concatenating instead of gathering result objects in a list and then running a single
pd.DataFrame()over it, but have kept it as is, as the performance improvement is negligible, and at least now it preserves parity