issue_comments
2 rows where issue = 300268334 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Fix precision drop when indexing a datetime64 arrays. · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 368703112 | https://github.com/pydata/xarray/pull/1942#issuecomment-368703112 | https://api.github.com/repos/pydata/xarray/issues/1942 | MDEyOklzc3VlQ29tbWVudDM2ODcwMzExMg== | fujiisoup 6815844 | 2018-02-27T00:36:14Z | 2018-02-27T00:36:14Z | MEMBER | It looks that numpy fails to cast I added a link to numpy's issue. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Fix precision drop when indexing a datetime64 arrays. 300268334 | |
| 368681609 | https://github.com/pydata/xarray/pull/1942#issuecomment-368681609 | https://api.github.com/repos/pydata/xarray/issues/1942 | MDEyOklzc3VlQ29tbWVudDM2ODY4MTYwOQ== | shoyer 1217238 | 2018-02-26T22:58:33Z | 2018-02-26T22:58:33Z | MEMBER | Were you able to identify the underlying issue? This feels like something that might likely be a bug in pandas or numpy. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Fix precision drop when indexing a datetime64 arrays. 300268334 |
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