issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 539648897 and user = 6628425 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

  • spencerkclark · 3 ✖

issue 1

  • interp with long cftime coordinates raises an error · 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
568223308 https://github.com/pydata/xarray/issues/3641#issuecomment-568223308 https://api.github.com/repos/pydata/xarray/issues/3641 MDEyOklzc3VlQ29tbWVudDU2ODIyMzMwOA== spencerkclark 6628425 2019-12-22T00:50:04Z 2019-12-22T00:50:04Z MEMBER

Thanks @maboualidev; I saw that @andersy005 posted about this too. I haven't had a chance to look deeply into your new package, but I am intrigued by the concept. I think patterns for working with data defined over intervals, be they in time or some other dimension, are something useful and should be explored.

1475 is a good thread in particular if you are interested in ideas for how cell boundaries (and operations that depend on them) might be represented most cleanly within xarray. Discussion there seems somewhat dormant at the moment, but I'd jump in there if you have comments, ideas, or questions.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   interp with long cftime coordinates raises an error 539648897
567085661 https://github.com/pydata/xarray/issues/3641#issuecomment-567085661 https://api.github.com/repos/pydata/xarray/issues/3641 MDEyOklzc3VlQ29tbWVudDU2NzA4NTY2MQ== spencerkclark 6628425 2019-12-18T15:40:19Z 2019-12-18T16:46:27Z MEMBER

That would indeed be a very clean approach (I don't know why that did not occur to me earlier!). In the past that kind of conversion used to have a bug, but it has been fixed as of NumPy 1.15 (see https://github.com/numpy/numpy/issues/11096).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   interp with long cftime coordinates raises an error 539648897
567020769 https://github.com/pydata/xarray/issues/3641#issuecomment-567020769 https://api.github.com/repos/pydata/xarray/issues/3641 MDEyOklzc3VlQ29tbWVudDU2NzAyMDc2OQ== spencerkclark 6628425 2019-12-18T12:58:23Z 2019-12-18T12:58:23Z MEMBER

Yes, there's a simple workaround for that at least, https://github.com/pydata/xarray/pull/3631#discussion_r359325745, but I agree it would be nice if we didn't need to worry about that.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   interp with long cftime coordinates raises an error 539648897

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