-
-
Notifications
You must be signed in to change notification settings - Fork 18.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
DOC: Handle exceptions when computing contributors. #23714
DOC: Handle exceptions when computing contributors. #23714
Conversation
Hello @TomAugspurger! Thanks for submitting the PR.
|
Codecov Report
@@ Coverage Diff @@
## master #23714 +/- ##
=======================================
Coverage 92.24% 92.24%
=======================================
Files 161 161
Lines 51336 51336
=======================================
Hits 47357 47357
Misses 3979 3979
Continue to review full report at Codecov.
|
https://travis-ci.org/pandas-dev/pandas/jobs/455318447#L2203 Ignoring the Azure failed build. Unfortunately, not even the 0.23.4..HEAD range is being picked up, but that's OK I think.
|
* upstream/master: BUG: to_html misses truncation indicators (...) when index=False (pandas-dev#22786) API/DEPR: replace "raise_conflict" with "errors" for df.update (pandas-dev#23657) BUG: Append DataFrame to Series with dateutil timezone (pandas-dev#23685) CLN/CI: Catch that stderr-warning! (pandas-dev#23706) ENH: Allow for join between two multi-index dataframe instances (pandas-dev#20356) Ensure Index._data is an ndarray (pandas-dev#23628) DOC: flake8-per-pr for windows users (pandas-dev#23707) DOC: Handle exceptions when computing contributors. (pandas-dev#23714) DOC: Validate space before colon docstring parameters pandas-dev#23483 (pandas-dev#23506) BUG-22984 Fix truncation of DataFrame representations (pandas-dev#22987)
* DOC: fix the build maybe
* DOC: fix the build maybe
* DOC: fix the build maybe
We're failing on master right now https://travis-ci.org/pandas-dev/pandas/jobs/455255389#L4369
I'm not sure why that is. Perhaps something with how the repo is cloned.
Anyway, this will work around the error.