-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Rename zerosum_axes
to n_zerosum_axes
#6522
Rename zerosum_axes
to n_zerosum_axes
#6522
Conversation
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.
LGTM, thanks @michaelraczycki ! I think it's your very first PR on this repo, so congrats 🍾
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #6522 +/- ##
===========================================
- Coverage 94.74% 75.64% -19.10%
===========================================
Files 146 147 +1
Lines 27807 27867 +60
===========================================
- Hits 26346 21081 -5265
- Misses 1461 6786 +5325
|
The doc fail is expected? |
@AlexAndorra I'm not sure. I'm not so familiar with this check, and I can't find a manual way to trigger it locally. From what I can see here in the description, it looks like it hits some kind of timeout. Could you give some advice on how to check it to ensure everything is ok? |
The ReadTheDocs has been failing with timeout in other places, so don't worry about it here. This failing test however has to be fixed: https://github.com/pymc-devs/pymc/actions/runs/4174655801/jobs/7321891536 |
…ly in the new param
It might be that the docs check was failing because the solution had a typo, which resulted in the zerosum_axes param not to be correctly saved into its new version (n_zerosum_axes). That caused the support_shape etc. not to get correct values and the corresponding tests to fail. If readthedocs checks test coverage then indeed it would fail because the typo caused 'new' parameter to appear and the tests were not testing stuff that was actually created. I'm not sure if I understand the check correctly, so in any case any suggestions that would help me get it better are highly appreciated! |
second mistake was not adapting unit tests, I noticed that they use the internal functions (ofc!) and I didn't switch the params used there to n_zerosum_axes, where inside the multivariate.py I did. Thus creating the "unexpected kwarg" error |
@AlexAndorra could you approve the checks again? I think it should work now |
zerosum_axes
to n_zerosum_axes
What is this PR about?
-added n_zerosum_axes parameter
-added backwards compatibility for previous parameter name
Major / Breaking Changes
New features
Bugfixes
Documentation
Maintenance