issue_comments

Table actions

3 rows where issue = 626215981 and user = 23738400 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

  • OriolAbril · 3 ✖

issue 1

  • keep attrs in reset_index · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
639752786 https://github.com/pydata/xarray/pull/4103#issuecomment-639752786 https://api.github.com/repos/pydata/xarray/issues/4103 MDEyOklzc3VlQ29tbWVudDYzOTc1Mjc4Ng== OriolAbril 23738400 2020-06-05T19:42:54Z 2020-06-05T19:42:54Z CONTRIBUTOR

Yep, I hope I'll have time for more to come :)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   keep attrs in reset_index 626215981
636020479 https://github.com/pydata/xarray/pull/4103#issuecomment-636020479 https://api.github.com/repos/pydata/xarray/issues/4103 MDEyOklzc3VlQ29tbWVudDYzNjAyMDQ3OQ== OriolAbril 23738400 2020-05-29T14:58:14Z 2020-05-29T14:58:14Z CONTRIBUTOR

Fixed tests. Now single index coordinates will keep their attributes when converted to non indexing coordinates.

I think changes in code would also make multi index keep their attributes, but I don't think multiindex can have attributes so it does not make any difference. I was wondering is this would be enough to close the original issue or if there is extra work to be done with multiindex.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   keep attrs in reset_index 626215981
635407227 https://github.com/pydata/xarray/pull/4103#issuecomment-635407227 https://api.github.com/repos/pydata/xarray/issues/4103 MDEyOklzc3VlQ29tbWVudDYzNTQwNzIyNw== OriolAbril 23738400 2020-05-28T15:03:53Z 2020-05-28T15:03:53Z CONTRIBUTOR

Thanks @dcherian! If there is anything I can do to help please say so. I don't really know where to start searching for this new error but I can run some tests or look into it if given some pointers. Whatever means less work for you.

Regarding current test, I can modify it so it does not trigger the bug and open an issue for this second bug. Is this ok or do yo prefer to tackle both in this PR?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   keep attrs in reset_index 626215981

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