-
Notifications
You must be signed in to change notification settings - Fork 17
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
1996 patch google symptoms #1999
Conversation
764f581
to
d46933b
Compare
There are a lot of changes here, so I'd recommend doing a comparison of output with this code vs with the old code to make sure they're the same (or vary in expected ways). |
at least for a daily run: there seems to be no change in the content of the output the log differ due to timestamps |
9dcc0f1
to
689d869
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Initial comments and questions. Still looking at logic.
2059ce6
to
45a2252
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some date padding questions, and a couple processing steps that seem too different between patch and normal production modes.
9727acf
to
f601a1d
Compare
1938ce7
to
f59b925
Compare
remove old code; not used anymore Co-authored-by: nmdefries <[email protected]>
1215753
to
f4981ea
Compare
f4981ea
to
528a1e3
Compare
@aysim319 I think the last set of comments didn't make it into this PR (or maybe I missed the commit?). Could you add those in on a separate PR? |
Description
Added new patching script along with refactoring code/ changing business logic
Associated Issue(s)