issue_comments
2 rows where author_association = "CONTRIBUTOR" and issue = 1114351614 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- [Bug]: reading NaT/NaN on M1 ARM chip · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1209664972 | https://github.com/pydata/xarray/issues/6191#issuecomment-1209664972 | https://api.github.com/repos/pydata/xarray/issues/6191 | IC_kwDOAMm_X85IGgXM | DocOtak 868027 | 2022-08-09T17:30:07Z | 2022-08-09T17:30:07Z | CONTRIBUTOR | Some additional info for when how to figure out the best way to address this. For the decode using pandas approach, two things I tried worked: using a pandas.array with a nullable integer data type, or simulating what happens on x86_64 systems by checking for nans in the incoming array and setting those positions to the pandas nullable integer array: ```python
``` The pandas solution is explicitly experimental in their docs, and the emulate version just feels "hacky" to me. These don't break any existing tests on my local machine. cftime itself has no support for nan type missing values and will fail: (on x86_64) ```python
cftime is happy with masked arrays: ```python
|
{ "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 | |
1209567966 | https://github.com/pydata/xarray/issues/6191#issuecomment-1209567966 | https://api.github.com/repos/pydata/xarray/issues/6191 | IC_kwDOAMm_X85IGIre | DocOtak 868027 | 2022-08-09T15:52:31Z | 2022-08-09T15:52:31Z | CONTRIBUTOR | I got caught by this one yesterday on an M1 machine. I did some digging and found what I think to be the underlying issue. The short explanation is that the time conversion functions do an I knew from my own data files that it wasn't the first element of the array being substituted but whatever was in the units as the epoch. I started to poke at the xarray internals (and the CFtime internals) to try to get a minimal example working, eventually found the following: On an M1: ```python
On an x86_64: ```python
This issue is not Apple/M1/clang specific, I tested on an aws graviton (arm) instance and got the same results with ubuntu/gcc: ```python Python 3.10.4 (main, Jun 29 2022, 12:14:53) [GCC 11.2.0] on linux Type "help", "copyright", "credits" or "license" for more information.
Here is where the cast is happening on the internal xarray implementation, CFtime has similar casts in its implementation. https://github.com/pydata/xarray/blob/8417f495e6b81a60833f86a978e5a8080a619aa0/xarray/coding/times.py#L237-L239 |
{ "total_count": 4, "+1": 2, "-1": 0, "laugh": 0, "hooray": 2, "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
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]);
user 1