issue_comments
4 rows where issue = 166642852 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- dtype changes after .load() · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 234126647 | https://github.com/pydata/xarray/issues/913#issuecomment-234126647 | https://api.github.com/repos/pydata/xarray/issues/913 | MDEyOklzc3VlQ29tbWVudDIzNDEyNjY0Nw== | shoyer 1217238 | 2016-07-21T00:49:01Z | 2016-07-21T00:49:01Z | MEMBER | I just filed a report upstream with dask in https://github.com/dask/dask/issues/1394. This is definitely a dask bug, because I can reproduce it without xarray. Thanks for the report! |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
dtype changes after .load() 166642852 | |
| 234097971 | https://github.com/pydata/xarray/issues/913#issuecomment-234097971 | https://api.github.com/repos/pydata/xarray/issues/913 | MDEyOklzc3VlQ29tbWVudDIzNDA5Nzk3MQ== | shoyer 1217238 | 2016-07-20T22:04:00Z | 2016-07-20T22:04:00Z | MEMBER | I would try creating a dask array of the same dtype and shape as this array. Then, see what happens to the dtype when you call the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
dtype changes after .load() 166642852 | |
| 234096888 | https://github.com/pydata/xarray/issues/913#issuecomment-234096888 | https://api.github.com/repos/pydata/xarray/issues/913 | MDEyOklzc3VlQ29tbWVudDIzNDA5Njg4OA== | robintw 296686 | 2016-07-20T21:59:14Z | 2016-07-20T21:59:14Z | CONTRIBUTOR | I'm not really sure how to work out which one it is a bug in - do you have any advice? Or should I just report it on the dask issue tracker too and see what they think? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
dtype changes after .load() 166642852 | |
| 234043551 | https://github.com/pydata/xarray/issues/913#issuecomment-234043551 | https://api.github.com/repos/pydata/xarray/issues/913 | MDEyOklzc3VlQ29tbWVudDIzNDA0MzU1MQ== | shoyer 1217238 | 2016-07-20T18:45:47Z | 2016-07-20T18:45:47Z | MEMBER | This is a bug, though possibly a dask.array bug rather than an xarray bug. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
dtype changes after .load() 166642852 |
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 2