issue_comments

Table actions

6 rows where user = 22488770 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: issue_url, reactions, created_at (date), updated_at (date)

user 1

  • andrewpauling · 6 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
700915602 https://github.com/pydata/xarray/pull/4454#issuecomment-700915602 https://api.github.com/repos/pydata/xarray/issues/4454 MDEyOklzc3VlQ29tbWVudDcwMDkxNTYwMg== andrewpauling 22488770 2020-09-29T18:56:17Z 2020-09-29T18:56:17Z CONTRIBUTOR

Cool! Thank you all for your help.

 
{
    "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
699190673 https://github.com/pydata/xarray/pull/4454#issuecomment-699190673 https://api.github.com/repos/pydata/xarray/issues/4454 MDEyOklzc3VlQ29tbWVudDY5OTE5MDY3Mw== andrewpauling 22488770 2020-09-25T22:33:45Z 2020-09-25T22:33:45Z CONTRIBUTOR

Thanks @spencerkclark, I have added a test with the decorator you mentioned and edited the formatting in the whats-new file as above. Hopefully it should be good now.

 
{
    "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
698507141 https://github.com/pydata/xarray/pull/4454#issuecomment-698507141 https://api.github.com/repos/pydata/xarray/issues/4454 MDEyOklzc3VlQ29tbWVudDY5ODUwNzE0MQ== andrewpauling 22488770 2020-09-24T18:17:52Z 2020-09-24T18:17:52Z CONTRIBUTOR

Nice! Could you also add a similar test for timedelta64 data?

Hi @spencerkclark, I have been trying to work on a test for timedelta64 data but I don't think I understand timedelta data very well. I can't seem to come up with an example that raises an OutOfBoundsTimedelta error. From what I found online (https://pandas.pydata.org/pandas-docs/stable/user_guide/timedeltas.html), the valid range for nanosecond precision should be about 100000 days. When I try to input an np.timedelta64[D] object of more days than that, it just overflows and gives nonsense without throwing an error. Do you have any suggestions?

 
{
    "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
698049781 https://github.com/pydata/xarray/pull/4454#issuecomment-698049781 https://api.github.com/repos/pydata/xarray/issues/4454 MDEyOklzc3VlQ29tbWVudDY5ODA0OTc4MQ== andrewpauling 22488770 2020-09-24T01:00:44Z 2020-09-24T01:00:44Z CONTRIBUTOR

Hi @max-sixty, I have just added what I hope is a good test, I haven't written one before, but tried to base it on others in the test_variable file

 
{
    "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
696258727 https://github.com/pydata/xarray/issues/4427#issuecomment-696258727 https://api.github.com/repos/pydata/xarray/issues/4427 MDEyOklzc3VlQ29tbWVudDY5NjI1ODcyNw== andrewpauling 22488770 2020-09-21T17:28:34Z 2020-09-21T17:28:34Z CONTRIBUTOR

Thanks @spencerkclark for the response, that makes sense. I have been able to get what I needed to work using cftime, it just seemed strange to me that xarray behaved as it did with datetime64.

I agree it would be nice if an error was raised when dates can't be represented, would this be difficult to implement? I have been hoping to contribute to some open-source projects so if it's not too complex I'd be happy to tackle it, and if you have any advice on where to start with this problem that would be great.

 
{
    "total_count": 2,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 2,
    "rocket": 0,
    "eyes": 0
}
   assign_coords with datetime64[us] changes dtype to datetime64[ns] 702373263
541979383 https://github.com/pydata/xarray/issues/3398#issuecomment-541979383 https://api.github.com/repos/pydata/xarray/issues/3398 MDEyOklzc3VlQ29tbWVudDU0MTk3OTM4Mw== andrewpauling 22488770 2019-10-15T00:01:37Z 2019-10-15T00:01:37Z CONTRIBUTOR

@jhamman yes, I just updated to v0.14 and the issue is still present

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Mean called on groupby object adds dimensions to undesired variables 506914634

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