issue_comments
4 rows where issue = 276241193 and user = 306380 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Windows/Python 2.7 tests of dask-distributed failing on master/v0.10.0 · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 346670364 | https://github.com/pydata/xarray/issues/1738#issuecomment-346670364 | https://api.github.com/repos/pydata/xarray/issues/1738 | MDEyOklzc3VlQ29tbWVudDM0NjY3MDM2NA== | mrocklin 306380 | 2017-11-23T17:22:26Z | 2017-11-23T17:22:26Z | MEMBER | It might be useful in the future to change one of XArray's test builds to be against git-master rather than latest release. This would help us to identify issues like this closer to when they occurred. On Thu, Nov 23, 2017 at 12:20 PM, Stephan Hoyer notifications@github.com wrote:
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Windows/Python 2.7 tests of dask-distributed failing on master/v0.10.0 276241193 | |
| 346634418 | https://github.com/pydata/xarray/issues/1738#issuecomment-346634418 | https://api.github.com/repos/pydata/xarray/issues/1738 | MDEyOklzc3VlQ29tbWVudDM0NjYzNDQxOA== | mrocklin 306380 | 2017-11-23T14:37:28Z | 2017-11-23T14:37:28Z | MEMBER | cc @pitrou in case this reminds him of anything On Thu, Nov 23, 2017 at 12:54 AM, Spencer Hill notifications@github.com wrote:
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Windows/Python 2.7 tests of dask-distributed failing on master/v0.10.0 276241193 | |
| 346510516 | https://github.com/pydata/xarray/issues/1738#issuecomment-346510516 | https://api.github.com/repos/pydata/xarray/issues/1738 | MDEyOklzc3VlQ29tbWVudDM0NjUxMDUxNg== | mrocklin 306380 | 2017-11-23T00:49:27Z | 2017-11-23T00:49:27Z | MEMBER | If I may generalize the question, did this start happening recently? Do we know what triggered this change? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Windows/Python 2.7 tests of dask-distributed failing on master/v0.10.0 276241193 | |
| 346510216 | https://github.com/pydata/xarray/issues/1738#issuecomment-346510216 | https://api.github.com/repos/pydata/xarray/issues/1738 | MDEyOklzc3VlQ29tbWVudDM0NjUxMDIxNg== | mrocklin 306380 | 2017-11-23T00:46:30Z | 2017-11-23T00:46:30Z | MEMBER | At first glance, no. Does this happen both on latest release and on git-master? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Windows/Python 2.7 tests of dask-distributed failing on master/v0.10.0 276241193 |
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