home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

4 rows where author_association = "MEMBER", issue = 723181209 and user = 6628425 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

  • spencerkclark · 4 ✖

issue 1

  • py38-upstream-dev failure: 'CFTimeIndex' object has no attribute '_id' · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
714845199 https://github.com/pydata/xarray/issues/4516#issuecomment-714845199 https://api.github.com/repos/pydata/xarray/issues/4516 MDEyOklzc3VlQ29tbWVudDcxNDg0NTE5OQ== spencerkclark 6628425 2020-10-23T01:08:50Z 2020-10-23T01:08:50Z MEMBER

Thanks to @topper-123's PR being merged upstream, this is now fixed. The next time our CI runs it should be green (I tested things out offline). If we want we can consider leveraging _id in CFTimeIndex later, but this particular issue can be closed.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  py38-upstream-dev failure: 'CFTimeIndex' object has no attribute '_id' 723181209
714146475 https://github.com/pydata/xarray/issues/4516#issuecomment-714146475 https://api.github.com/repos/pydata/xarray/issues/4516 MDEyOklzc3VlQ29tbWVudDcxNDE0NjQ3NQ== spencerkclark 6628425 2020-10-22T01:30:25Z 2020-10-22T01:30:25Z MEMBER

Thanks @topper-123 -- I see you also made https://github.com/pandas-dev/pandas/pull/37321, making Index._id optional again, which I appreciate!

We do rely on private attributes in some places, but we're typically cautious about doing that, because their behavior can change without warning. For instance, in this case pandas-dev/pandas#37087 would have been a breaking change in a different way, since _reset_identity went from returning an Index, to operating on the Index in place.

Looking at the history of pandas.Index, it generally seems like outside the recent change, _reset_identity has been pretty stable over the years, though we'd still need to mull over the trade-off between the performance benefit and the robustness of the subclass to changes in pandas.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  py38-upstream-dev failure: 'CFTimeIndex' object has no attribute '_id' 723181209
711100380 https://github.com/pydata/xarray/issues/4516#issuecomment-711100380 https://api.github.com/repos/pydata/xarray/issues/4516 MDEyOklzc3VlQ29tbWVudDcxMTEwMDM4MA== spencerkclark 6628425 2020-10-18T00:54:31Z 2020-10-18T00:54:31Z MEMBER

I posted a question in the pandas repo related to this: https://github.com/pandas-dev/pandas/issues/37213.

{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  py38-upstream-dev failure: 'CFTimeIndex' object has no attribute '_id' 723181209
711022646 https://github.com/pydata/xarray/issues/4516#issuecomment-711022646 https://api.github.com/repos/pydata/xarray/issues/4516 MDEyOklzc3VlQ29tbWVudDcxMTAyMjY0Ng== spencerkclark 6628425 2020-10-17T14:42:42Z 2020-10-17T14:44:21Z MEMBER

Indeed a bisect reveals pandas-dev/pandas#37087 was the cause: ``` abd3acf05516611e9e90d57ae363f1567e30f49a is the first bad commit commit abd3acf05516611e9e90d57ae363f1567e30f49a Author: Terji Petersen contribute@tensortable.com Date: Wed Oct 14 13:26:45 2020 +0100

CLN: clean Index._id (#37087)

pandas/core/indexes/base.py | 21 +++++++++++++-------- pandas/core/indexes/multi.py | 4 +++- pandas/tests/arithmetic/test_object.py | 3 ++- 3 files changed, 18 insertions(+), 10 deletions(-) ```

I think it's that _id used to automatically be initialized to None and now it needs to be explicitly initialized within the constructor. They added some try-except logic in the is_ method to handle the case where _id has not been initialized, but there's an error happening now within the view method. Here's a more minimal example:

``` In [1]: import xarray as xr

In [2]: xr.cftime_range("2000", periods=2).view()

AttributeError Traceback (most recent call last) <ipython-input-2-5226cd5e3bc1> in <module> ----> 1 xr.cftime_range("2000", periods=2).view()

~/Software/pandas/pandas/core/indexes/base.py in view(self, cls) 630 result = self._shallow_copy() 631 if isinstance(result, Index): --> 632 result._id = self._id 633 return result 634

AttributeError: 'CFTimeIndex' object has no attribute '_id' ```

I'll have to think about things a little more to see if we should pursue an upstream fix or whether we can address it in xarray.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  py38-upstream-dev failure: 'CFTimeIndex' object has no attribute '_id' 723181209

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);
Powered by Datasette · Queries took 28.81ms · About: xarray-datasette