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
[BUGFIX] expect_day_count_to_be_close_to_equivalent_week_day_mean #7782
[BUGFIX] expect_day_count_to_be_close_to_equivalent_week_day_mean #7782
Conversation
✅ Deploy Preview for niobium-lead-7998 canceled.
|
Hello @HadasManor can you pull in the latest changes from develop and resolve your merge conflicts. Can you also restore the deleted file? Thanks. |
Hi @kenwade4 , I also wrote you in slack about this, I did pull the latest changes and there are still conflicts so I am not sure what is happening (also the Regarding the deleted file- as I wrote in the PR description, this is an old expectation that has changed names (to the other file here), and should not have stayed. It is the same, except the deleted file is not updated and contains bugs. For the benefit of our users, it needs to be deleted |
@HadasManor the button is greyed out when the conflict cannot be resolved automatically
I'd guess to keep the chunk that uses
You will also need to update the |
1ca6ece
into
great-expectations:develop
Please annotate your PR title to describe what the PR does, then give a brief bulleted description of your PR below. PR titles should begin with [BUGFIX], [FEATURE], [DOCS], [MAINTENANCE], or [CONTRIB]. If a new feature introduces breaking changes for the Great Expectations API or configuration files, please also add [BREAKING]. You can read about the tags in our contributor checklist.
Changes proposed in this pull request:
Fixed bug in
expect_day_count_to_be_close_to_equivalent_week_day_mean
Deleted old expectation that was replaced by
expect_day_count_to_be_close_to_equivalent_week_day_mean
(same expectation but better name and with fixed bugs)My code follows the Great Expectations style guide
I have performed a self-review of my own code
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
I have added unit tests where applicable and made sure that new and existing tests are passing.
I have run any local integration tests and made sure that nothing is broken.