issue_comments
6 rows where issue = 229138906 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- fixed dask prefix naming · 6 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
303213597 | https://github.com/pydata/xarray/pull/1411#issuecomment-303213597 | https://api.github.com/repos/pydata/xarray/issues/1411 | MDEyOklzc3VlQ29tbWVudDMwMzIxMzU5Nw== | shoyer 1217238 | 2017-05-22T20:39:01Z | 2017-05-22T20:39:01Z | MEMBER | Thanks @rabernat ! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixed dask prefix naming 229138906 | |
302147200 | https://github.com/pydata/xarray/pull/1411#issuecomment-302147200 | https://api.github.com/repos/pydata/xarray/issues/1411 | MDEyOklzc3VlQ29tbWVudDMwMjE0NzIwMA== | rabernat 1197350 | 2017-05-17T16:34:56Z | 2017-05-17T16:34:56Z | MEMBER | Ok, I think I fixed it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixed dask prefix naming 229138906 | |
302130344 | https://github.com/pydata/xarray/pull/1411#issuecomment-302130344 | https://api.github.com/repos/pydata/xarray/issues/1411 | MDEyOklzc3VlQ29tbWVudDMwMjEzMDM0NA== | shoyer 1217238 | 2017-05-17T15:38:13Z | 2017-05-17T15:38:13Z | MEMBER |
Actually, apparently not necessarily -- look a few lines further up to where it is defined. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixed dask prefix naming 229138906 | |
302127457 | https://github.com/pydata/xarray/pull/1411#issuecomment-302127457 | https://api.github.com/repos/pydata/xarray/issues/1411 | MDEyOklzc3VlQ29tbWVudDMwMjEyNzQ1Nw== | rabernat 1197350 | 2017-05-17T15:29:27Z | 2017-05-17T15:29:27Z | MEMBER |
I thought that was already happening. Here is the token
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixed dask prefix naming 229138906 | |
302124807 | https://github.com/pydata/xarray/pull/1411#issuecomment-302124807 | https://api.github.com/repos/pydata/xarray/issues/1411 | MDEyOklzc3VlQ29tbWVudDMwMjEyNDgwNw== | shoyer 1217238 | 2017-05-17T15:21:01Z | 2017-05-17T15:21:01Z | MEMBER | Note that the test failures are also showing different numbers from I think this is actually a problem with providing unique names for dask. Previously, the filename ended up as part of the prefix explicitly, but now it needs to be explicitly included as input to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixed dask prefix naming 229138906 | |
301904032 | https://github.com/pydata/xarray/pull/1411#issuecomment-301904032 | https://api.github.com/repos/pydata/xarray/issues/1411 | MDEyOklzc3VlQ29tbWVudDMwMTkwNDAzMg== | rabernat 1197350 | 2017-05-16T20:22:30Z | 2017-05-16T20:22:30Z | MEMBER | This seems to be interacting badly with @pwolfram: can you give any insight into what might be going on? This is an interesting trace from travis: https://travis-ci.org/pydata/xarray/jobs/232969599#L3368 ``` xarray/tests/init.py:153: in assertDatasetIdentical assert_identical(d1, d2) a = <[AssertionError("internal failure: file must be open if Does autoclose assume that the dask object names actually match the filenames? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixed dask prefix naming 229138906 |
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