issue_comments

Table actions

2 rows where issue = 707745196 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 · 2 ✖

issue 1

  • Raise error when datetime64 or timedelta64 values that are outside the valid range for ns precision are converted to ns precision · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
701095631 https://github.com/pydata/xarray/pull/4454#issuecomment-701095631 https://api.github.com/repos/pydata/xarray/issues/4454 MDEyOklzc3VlQ29tbWVudDcwMTA5NTYzMQ== spencerkclark 6628425 2020-09-30T00:50:55Z 2020-09-30T00:50:55Z MEMBER

Thanks again @andrewpauling!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Raise error when datetime64 or timedelta64 values that are outside the valid range for ns precision are converted to ns precision 707745196
698670864 https://github.com/pydata/xarray/pull/4454#issuecomment-698670864 https://api.github.com/repos/pydata/xarray/issues/4454 MDEyOklzc3VlQ29tbWVudDY5ODY3MDg2NA== spencerkclark 6628425 2020-09-25T01:30:05Z 2020-09-25T23:56:23Z MEMBER

You're absolutely right @andrewpauling -- pandas currently doesn't seem to have overflow protection in the case of casting timedelta64 types. I wrongly assumed that it would! I went ahead and opened an issue there: https://github.com/pandas-dev/pandas/issues/36615. We'll see what they say.

For now maybe you can add the test and attach an expected failure decorator to it?

In researching this, I came across https://github.com/numpy/numpy/issues/16352; if that eventually gets addressed this might all be moot.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Raise error when datetime64 or timedelta64 values that are outside the valid range for ns precision are converted to ns precision 707745196

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