issue_comments

Table actions

4 rows where author_association = "MEMBER" and issue = 1389176083 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • Don't cast NaN to integer · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1263671832 https://github.com/pydata/xarray/pull/7098#issuecomment-1263671832 https://api.github.com/repos/pydata/xarray/issues/7098 IC_kwDOAMm_X85LUhoY dcherian 2448579 2022-09-30T14:47:06Z 2022-09-30T14:47:06Z MEMBER

I think the real solution here is to explicitly handle NaNs during the decoding step. We do want these to be NaT in the output.

cc @spencerclark

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't cast NaN to integer 1389176083
1262836815 https://github.com/pydata/xarray/pull/7098#issuecomment-1262836815 https://api.github.com/repos/pydata/xarray/issues/7098 IC_kwDOAMm_X85LRVxP TomNicholas 35968931 2022-09-29T21:28:31Z 2022-09-29T21:28:31Z MEMBER

Thank you very much for the context @DocOtak !

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't cast NaN to integer 1389176083
1262579935 https://github.com/pydata/xarray/pull/7098#issuecomment-1262579935 https://api.github.com/repos/pydata/xarray/issues/7098 IC_kwDOAMm_X85LQXDf TomNicholas 35968931 2022-09-29T17:20:48Z 2022-09-29T17:20:48Z MEMBER

It's already perfectly covered by the testsuite.

Okay great, but then why are these tests failing for you (locally?) and not in our CI runs? (Our main branch just passed all automated tests just now.) Do you have a different version of some package that we aren't testing against?

I'm asking because if our current CI test runs don't reproduce this error, then we (a) have no way to check that your change fixed the error and (b) will not know if some regression causes this error to resurface in future. Standard practice would be to raise an issue that demonstrates the problem, then link the fix PR to that issue.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't cast NaN to integer 1389176083
1262537736 https://github.com/pydata/xarray/pull/7098#issuecomment-1262537736 https://api.github.com/repos/pydata/xarray/issues/7098 IC_kwDOAMm_X85LQMwI TomNicholas 35968931 2022-09-29T16:44:38Z 2022-09-29T16:44:38Z MEMBER

Hi @andreas-schwab, and welcome to xarray!

Can you tell what specific failures this change fixed for you? If there was something failing we want to capture it in our test suite, but I am not sure what failure you are referring to.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Don't cast NaN to integer 1389176083

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