issue_comments

Table actions

3 rows where author_association = "MEMBER" and issue = 1114351614 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

issue 1

  • [Bug]: reading NaT/NaN on M1 ARM chip · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1133765720 https://github.com/pydata/xarray/issues/6191#issuecomment-1133765720 https://api.github.com/repos/pydata/xarray/issues/6191 IC_kwDOAMm_X85Dk-RY max-sixty 5635139 2022-05-21T20:43:08Z 2022-05-21T20:43:08Z MEMBER

I sorted out my M1 python installation and can reproduce: In [21]: ds_r.time Out[21]: <xarray.DataArray 'time' (nt: 10)> array(['2022-01-01T00:00:00.000000000', '2022-01-02T00:00:00.000000000', '2022-01-03T00:00:00.000000000', '2022-01-04T00:00:00.000000000', '2022-01-01T00:00:00.000000000', '2022-01-06T00:00:00.000000000', # Note the first value on this line! '2022-01-07T00:00:00.000000000', '2022-01-08T00:00:00.000000000', '2022-01-09T00:00:00.000000000', '2022-01-10T00:00:00.000000000'], dtype='datetime64[ns]') Dimensions without coordinates: nt

It's quite surprising we get '2022-01-01T00:00:00.000000000' rather than NaT — why the beginning of the year?!

I suspect it's not directly an xarray issue given Xarray is only python code, and python code does not directly branch by CPU. I've frequently had issues like this where it's difficult to understand which library is responsible, I'd welcome any more investigation here.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [Bug]: reading NaT/NaN on M1 ARM chip 1114351614
1021889497 https://github.com/pydata/xarray/issues/6191#issuecomment-1021889497 https://api.github.com/repos/pydata/xarray/issues/6191 IC_kwDOAMm_X8486MvZ max-sixty 5635139 2022-01-26T05:53:43Z 2022-01-26T05:53:43Z MEMBER

I tried reproducing on an M1 Mac, but my install of python seems to report that it's on an x86_64 (version='Darwin Kernel Version 21.0.1: Tue Sep 14 20:56:24 PDT 2021 ; root:xnu-8019.30.61~4/RELEASE_ARM64_T6000', machine='x86_64'). It didn't reproduce, unsurprisingly.

Does uninstalling netCDF4 help? That would isolate it to that library and its dependencies.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [Bug]: reading NaT/NaN on M1 ARM chip 1114351614
1021609794 https://github.com/pydata/xarray/issues/6191#issuecomment-1021609794 https://api.github.com/repos/pydata/xarray/issues/6191 IC_kwDOAMm_X8485IdC max-sixty 5635139 2022-01-25T21:08:02Z 2022-01-25T21:08:02Z MEMBER

Thanks @philippemiron .

My guess is that this is an issue with an underlying library, since xarray doesn't generally do these operations in its code. Do you know if there are any similar issues in libnetcdf or netCDF4?

(Others know more than me about these libraries, so please feel free to interject)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [Bug]: reading NaT/NaN on M1 ARM chip 1114351614

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