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/issues/6941#issuecomment-1274969028,https://api.github.com/repos/pydata/xarray/issues/6941,1274969028,IC_kwDOAMm_X85L_nvE,2448579,2022-10-11T16:31:46Z,2022-10-11T16:31:46Z,MEMBER,Closing since our action keeps updating the message and the discussion isn't relevant any more.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1345644028
https://github.com/pydata/xarray/issues/6941#issuecomment-1263288581,https://api.github.com/repos/pydata/xarray/issues/6941,1263288581,IC_kwDOAMm_X85LTEEF,32801740,2022-09-30T08:43:47Z,2022-09-30T08:50:06Z,CONTRIBUTOR,"The last run reports (development) version 2022.9.1.dev3+g341f1302 of xarray (derived from the most recent tag 2022.9.0).

I assume you have seen version 0.18.x in your personal fork. I have seen  similar problems where version 0.16.x of xarray was shown. The culprit seems to be that the github button for syncing your fork with the upstream repo doesn't update tags. It only contains the tags from back when you created the fork. I updated the tags manually using something like
```
git fetch --tags upstream
git push --tags origin
```
which did the trick for me.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1345644028
https://github.com/pydata/xarray/issues/6941#issuecomment-1263157424,https://api.github.com/repos/pydata/xarray/issues/6941,1263157424,IC_kwDOAMm_X85LSkCw,43316012,2022-09-30T06:24:43Z,2022-09-30T06:24:43Z,COLLABORATOR,"The current failures are because the installed xarray seems to have version 0.18.x and pandas requires >= 0.19

Is that a bug in setuptools?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1345644028
https://github.com/pydata/xarray/issues/6941#issuecomment-1233350295,https://api.github.com/repos/pydata/xarray/issues/6941,1233350295,IC_kwDOAMm_X85Jg26X,302469,2022-08-31T19:44:24Z,2022-08-31T19:44:24Z,CONTRIBUTOR,"IIUC, I think this is the exception those tests are trying to check:
https://github.com/pydata/xarray/blob/4880012ddee9e43e3e18e95551876e9c182feafb/xarray/plot/utils.py#L893-L896","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1345644028
https://github.com/pydata/xarray/issues/6941#issuecomment-1233345322,https://api.github.com/repos/pydata/xarray/issues/6941,1233345322,IC_kwDOAMm_X85Jg1sq,302469,2022-08-31T19:38:24Z,2022-08-31T19:38:24Z,CONTRIBUTOR,"We looked at this downstream in Matplotlib to see if we introduced something in 3.6.0rc2. There was a bug there in that exception types changed unexpectedly.

However, I am thinking that these two tests are incorrect. They are generically checking for `ValueError` without a match on the exception text. This means they completely missed the fact that `husl` was an invalid colormap (which was only exposed because 3.6.0rc2 accidentally changed the type for that exception), whereas I think it was only supposed to check that `levels` was not specified.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1345644028