issue_comments

Table actions

3 rows where issue = 407864596 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

  • silence warning for decode_cf_datetime? · 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
462098888 https://github.com/pydata/xarray/issues/2754#issuecomment-462098888 https://api.github.com/repos/pydata/xarray/issues/2754 MDEyOklzc3VlQ29tbWVudDQ2MjA5ODg4OA== spencerkclark 6628425 2019-02-10T02:53:23Z 2019-02-10T02:53:23Z MEMBER

What is still missing once 0.12 is released (plotting and resampling)? I don't have the full overview there.

@mathause indeed we've made a lot of progress. A few remaining missing things that come to mind (there could be others) are: - Support for missing values in arrays of cftime objects (I should probably create an issue for this) - Possible PeriodIndex-like functionality with cftime objects (#2481) - coarsen (coming in the next version of xarray) still needs to be updated to work with cftime coordinates (waiting on #2668 before starting on that)

Out of those three, coarsen is probably the highest priority on my list at the moment (the other two would require some more careful thought). 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   silence warning for decode_cf_datetime? 407864596
462098476 https://github.com/pydata/xarray/issues/2754#issuecomment-462098476 https://api.github.com/repos/pydata/xarray/issues/2754 MDEyOklzc3VlQ29tbWVudDQ2MjA5ODQ3Ng== spencerkclark 6628425 2019-02-10T02:42:12Z 2019-02-10T02:42:12Z MEMBER

Thanks for your thoughts @shoyer; I like your suggested approach.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   silence warning for decode_cf_datetime? 407864596
461814892 https://github.com/pydata/xarray/issues/2754#issuecomment-461814892 https://api.github.com/repos/pydata/xarray/issues/2754 MDEyOklzc3VlQ29tbWVudDQ2MTgxNDg5Mg== spencerkclark 6628425 2019-02-08T14:11:53Z 2019-02-08T14:11:53Z MEMBER

Thanks @mathause -- I'm assuming you are referring to this warning, rather than an error? //anaconda/envs/xarray-dev-37/bin/ipython:2: SerializationWarning: Unable to decode time axis into full numpy.datetime64 objects, continuing using dummy cftime.datetime objects instead, reason: dates out of range The rationale for keeping this warning is that for standard calendars (like 'proleptic_gregorian') we use pandas/NumPy dates by default; therefore falling back to using cftime in this circumstance is a deviation from the default behavior, which might come as a surprise to some users.

I wonder if it might make sense to offer an option in xarray to always decode times to cftime dates, even for standard calendar dates between years 1678 and 2262 (which, if set, could also silence this warning); this would be another possible solution for #1263.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   silence warning for decode_cf_datetime? 407864596

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