-
Notifications
You must be signed in to change notification settings - Fork 834
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
fix: Add TreatmentCol Type check at the very beginning #1816
Conversation
Hey @dylanw-oss 👋! We use semantic commit messages to streamline the release process. Examples of commit messages with semantic prefixes:
To test your commit locally, please follow our guild on building from source. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Codecov Report
@@ Coverage Diff @@
## master #1816 +/- ##
===========================================
- Coverage 86.80% 76.04% -10.76%
===========================================
Files 295 295
Lines 15387 15396 +9
Branches 777 794 +17
===========================================
- Hits 13356 11708 -1648
- Misses 2031 3688 +1657
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
What changes are proposed in this pull request?
If customer's dataset Treatment column is boolean type, it will throw exception now due to residual computation can't be performed on boolean data type. This change is to convert it to integer type internally.