issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 256496917 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • shoyer · 3 ✖

issue 1

  • Regression: time attributes on PeriodIndex · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
328654477 https://github.com/pydata/xarray/issues/1565#issuecomment-328654477 https://api.github.com/repos/pydata/xarray/issues/1565 MDEyOklzc3VlQ29tbWVudDMyODY1NDQ3Nw== shoyer 1217238 2017-09-11T20:50:16Z 2017-09-11T20:50:16Z MEMBER

It's only an dtype=object array externally: internally, the data is still stored as a pandas.PeriodIndex. I think you'll find that inside ref_var._data.array .

Potentially we could some sort of API for surfacing this information, e.g., a pandas_dtype property to xarray.Variable.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Regression: time attributes on PeriodIndex 256496917
328573731 https://github.com/pydata/xarray/issues/1565#issuecomment-328573731 https://api.github.com/repos/pydata/xarray/issues/1565 MDEyOklzc3VlQ29tbWVudDMyODU3MzczMQ== shoyer 1217238 2017-09-11T15:54:19Z 2017-09-11T15:54:19Z MEMBER

Looks like https://github.com/pydata/xarray/pull/1356, which introduced a is_datatime_like() check to the dtype of a variable before adding time components.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Regression: time attributes on PeriodIndex 256496917
328400022 https://github.com/pydata/xarray/issues/1565#issuecomment-328400022 https://api.github.com/repos/pydata/xarray/issues/1565 MDEyOklzc3VlQ29tbWVudDMyODQwMDAyMg== shoyer 1217238 2017-09-11T02:31:41Z 2017-09-11T02:31:41Z MEMBER

I never intended to support time attributes on PeriodIndex objects so there was never any test coverage here, but I guess it has been working! Nonetheless this should be pretty easy to fix.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Regression: time attributes on PeriodIndex 256496917

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]);