issue_comments
5 rows where issue = 268264252 and user = 2443309 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- fixes for warnings related to unit tests and nan comparisons · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
340240917 | https://github.com/pydata/xarray/pull/1657#issuecomment-340240917 | https://api.github.com/repos/pydata/xarray/issues/1657 | MDEyOklzc3VlQ29tbWVudDM0MDI0MDkxNw== | jhamman 2443309 | 2017-10-29T06:33:08Z | 2017-10-29T06:33:08Z | MEMBER | @shoyer - I think this is all good now. We seem to have acquired another unrelated build failures though... |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixes for warnings related to unit tests and nan comparisons 268264252 | |
340122183 | https://github.com/pydata/xarray/pull/1657#issuecomment-340122183 | https://api.github.com/repos/pydata/xarray/issues/1657 | MDEyOklzc3VlQ29tbWVudDM0MDEyMjE4Mw== | jhamman 2443309 | 2017-10-27T23:44:37Z | 2017-10-27T23:44:37Z | MEMBER | @shoyer - updated. If all the tests pass, I'll merge tonight. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixes for warnings related to unit tests and nan comparisons 268264252 | |
340067233 | https://github.com/pydata/xarray/pull/1657#issuecomment-340067233 | https://api.github.com/repos/pydata/xarray/issues/1657 | MDEyOklzc3VlQ29tbWVudDM0MDA2NzIzMw== | jhamman 2443309 | 2017-10-27T19:42:33Z | 2017-10-27T19:42:33Z | MEMBER | Okay, so this knocks off the lowest hanging fruit. I'll pull the pytest error out of the travis build and we'll move forward with this. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixes for warnings related to unit tests and nan comparisons 268264252 | |
340064856 | https://github.com/pydata/xarray/pull/1657#issuecomment-340064856 | https://api.github.com/repos/pydata/xarray/issues/1657 | MDEyOklzc3VlQ29tbWVudDM0MDA2NDg1Ng== | jhamman 2443309 | 2017-10-27T19:31:43Z | 2017-10-27T19:31:43Z | MEMBER | @shoyer - I'm wondering if we should attack #1652 in stages. The remaining warnings are going to take a bit more effort and this first block included a lot of line changes. I'm a bit concerned that if we let this sit, we will end up with a million merge conflicts. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixes for warnings related to unit tests and nan comparisons 268264252 | |
339224835 | https://github.com/pydata/xarray/pull/1657#issuecomment-339224835 | https://api.github.com/repos/pydata/xarray/issues/1657 | MDEyOklzc3VlQ29tbWVudDMzOTIyNDgzNQ== | jhamman 2443309 | 2017-10-25T06:08:57Z | 2017-10-25T06:08:57Z | MEMBER | Down to 96 (was 372) warnings in my py36 test environment. Two changes that I could uses some input on: 1 - Numpy element wise comparison```Python def assertEqual(self, a1, a2):
@shoyer - you and I put together the assertEqual method a while back. Do we need to check the size of arrays before comparing the values? 2 - Numpy invalid value comparisone.g.:
I'm hoping there is a succinct way of wrapping many of our nan comparing functions in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
fixes for warnings related to unit tests and nan comparisons 268264252 |
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