issue_comments

Table actions

3 rows where issue = 139956689 and user = 4295853 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

  • pwolfram · 3 ✖

issue 1

  • Time limitation (between years 1678 and 2262) restrictive to climate community · 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
194973785 https://github.com/pydata/xarray/issues/789#issuecomment-194973785 https://api.github.com/repos/pydata/xarray/issues/789 MDEyOklzc3VlQ29tbWVudDE5NDk3Mzc4NQ== pwolfram 4295853 2016-03-10T17:47:10Z 2016-03-10T17:47:10Z CONTRIBUTOR

Thank you very much @shoyer for your very fast reply. If we fixed the issue in pandas (e.g., your 1) would that be sufficient to resolve the issue or do we also need to enhance datetime64 also (e.g., your 2)? What is your recommendation on the best way to proceed and is it even reasonable to do so?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Time limitation (between years 1678 and 2262) restrictive to climate community 139956689
194966713 https://github.com/pydata/xarray/issues/789#issuecomment-194966713 https://api.github.com/repos/pydata/xarray/issues/789 MDEyOklzc3VlQ29tbWVudDE5NDk2NjcxMw== pwolfram 4295853 2016-03-10T17:27:01Z 2016-03-10T17:27:01Z CONTRIBUTOR

See also https://github.com/pydata/xarray/issues/531 (cc @jsbj, @darothen, @jhamman); https://github.com/pydata/xarray/issues/521 (cc @rabernat, @jhamman)

It appears this is an issue with the numpy datetime64 API (https://github.com/numpy/numpy/issues/6207).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Time limitation (between years 1678 and 2262) restrictive to climate community 139956689
194964987 https://github.com/pydata/xarray/issues/789#issuecomment-194964987 https://api.github.com/repos/pydata/xarray/issues/789 MDEyOklzc3VlQ29tbWVudDE5NDk2NDk4Nw== pwolfram 4295853 2016-03-10T17:22:11Z 2016-03-10T17:22:11Z CONTRIBUTOR

@jhamman and @shoyer, do you know if more general support for times will be provided?

I would say this is a potential roadblock inhibiting easy adoption of this library within the climate community. For example, this is creating problems when we setup and analyze climate models (cc @akturner, @douglasjacobsen, @milenaveneziani). There are obvious work arounds, but they are hacks, e.g., I just add 1700 or some arbitrary year within my wrapper to MPAS at https://github.com/pwolfram/mpas_xarray_wrapper. However, this does not appear to be a viable long-term solution.

Does anyone have some advice on how to better deal with this problem?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Time limitation (between years 1678 and 2262) restrictive to climate community 139956689

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