home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 553392712

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/pull/3516#issuecomment-553392712 https://api.github.com/repos/pydata/xarray/issues/3516 553392712 MDEyOklzc3VlQ29tbWVudDU1MzM5MjcxMg== 14808389 2019-11-13T12:56:50Z 2019-11-13T18:29:16Z MEMBER

CI: I think it's possible using sphinx-build -W --keep-going, which continues as normal and returns a non-zero error code if a warning was emitted, but first we need to stamp out all warnings (otherwise we have a lot of failing checks on unrelated PRs).

I also noticed the CI uses -n for a nit-picky mode that increases the number of emitted warnings, so now I know where the extra warnings come from.

numpy: sure, but updating upstream is only a long term fix, we will still have to somehow ignore these warnings if we want to check for new warnings using CI.

Edit: the warning about files not included by any toctree can be silenced by adding :orphan: to the top of the file (see documentation and this question on SO)

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  521887948
Powered by Datasette · Queries took 2.519ms · About: xarray-datasette