issue_comments
5 rows where issue = 200908727 and user = 10050469 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Test failures on Debian if built with bottleneck · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
275956940 | https://github.com/pydata/xarray/issues/1208#issuecomment-275956940 | https://api.github.com/repos/pydata/xarray/issues/1208 | MDEyOklzc3VlQ29tbWVudDI3NTk1Njk0MA== | fmaussion 10050469 | 2017-01-29T23:56:04Z | 2017-01-29T23:56:04Z | MEMBER | I added a PR in order to allow a dev version of bottleneck to be used, too: https://github.com/pydata/xarray/issues/1235 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Test failures on Debian if built with bottleneck 200908727 | |
275955256 | https://github.com/pydata/xarray/issues/1208#issuecomment-275955256 | https://api.github.com/repos/pydata/xarray/issues/1208 | MDEyOklzc3VlQ29tbWVudDI3NTk1NTI1Ng== | fmaussion 10050469 | 2017-01-29T23:28:18Z | 2017-01-29T23:28:18Z | MEMBER | the tests now pass with bottleneck master. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Test failures on Debian if built with bottleneck 200908727 | |
275910605 | https://github.com/pydata/xarray/issues/1208#issuecomment-275910605 | https://api.github.com/repos/pydata/xarray/issues/1208 | MDEyOklzc3VlQ29tbWVudDI3NTkxMDYwNQ== | fmaussion 10050469 | 2017-01-29T12:26:03Z | 2017-01-29T12:26:03Z | MEMBER | @shoyer nevermind, I found the bug: https://github.com/kwgoodman/bottleneck/issues/161 Quite a tricky one indeed ;-) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Test failures on Debian if built with bottleneck 200908727 | |
275909069 | https://github.com/pydata/xarray/issues/1208#issuecomment-275909069 | https://api.github.com/repos/pydata/xarray/issues/1208 | MDEyOklzc3VlQ29tbWVudDI3NTkwOTA2OQ== | fmaussion 10050469 | 2017-01-29T11:53:27Z | 2017-01-29T11:53:27Z | MEMBER | @shoyer there is something very weird going on. See the following example: ```python import numpy as np import bottleneck as bn import xarray as xr da = xr.DataArray(np.ones((10, 20)).astype(np.int), dims=['x', 'y'],
coords={'abc':('y', np.array(['a'] * 9 + ['c'] + ['b'] * 10))})
np.testing.assert_allclose(np.sum(da[:, 9:10]), bn.nansum(da[:, 9:10])) # this will allways work
np.testing.assert_allclose(da.groupby('abc').reduce(np.sum), da.groupby('abc').sum()) # this won't
```AssertionError Traceback (most recent call last) <ipython-input-95-d34b19396eb5> in <module>() 2 coords={'abc':('y', np.array(['a'] * 9 + ['c'] + ['b'] * 10))}) 3 np.testing.assert_allclose(np.sum(da[:, 9:10]), bn.nansum(da[:, 9:10])) ----> 4 np.testing.assert_allclose(da.groupby('abc').reduce(np.sum), da.groupby('abc').sum()) /home/mowglie/.pyvirtualenvs/py3/lib/python3.4/site-packages/numpy/testing/utils.py in assert_allclose(actual, desired, rtol, atol, equal_nan, err_msg, verbose) 1409 header = 'Not equal to tolerance rtol=%g, atol=%g' % (rtol, atol) 1410 assert_array_compare(compare, actual, desired, err_msg=str(err_msg), -> 1411 verbose=verbose, header=header, equal_nan=equal_nan) 1412 1413 /home/mowglie/.pyvirtualenvs/py3/lib/python3.4/site-packages/numpy/testing/utils.py in assert_array_compare(comparison, x, y, err_msg, verbose, header, precision, equal_nan) 794 names=('x', 'y'), precision=precision) 795 if not cond: --> 796 raise AssertionError(msg) 797 except ValueError: 798 import traceback AssertionError: Not equal to tolerance rtol=1e-07, atol=0 (mismatch 33.33333333333333%) x: array([ 90., 100., 10.]) y: array([ 90., 100., 1.]) ``` So the new operation is applied only to the first element of the grouped selection, and I didn't manage to us bottleneck only to replicate this (since the first assertion always passes). Before I dig into this I'd like to have your opinion on this: any idea on what could go wrong here? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Test failures on Debian if built with bottleneck 200908727 | |
275396760 | https://github.com/pydata/xarray/issues/1208#issuecomment-275396760 | https://api.github.com/repos/pydata/xarray/issues/1208 | MDEyOklzc3VlQ29tbWVudDI3NTM5Njc2MA== | fmaussion 10050469 | 2017-01-26T14:10:48Z | 2017-01-26T14:10:48Z | MEMBER | I can confirm that - I have the same problems on my pip virtualenv on linux mint (I tried to reproduce it on travis without success) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Test failures on Debian if built with bottleneck 200908727 |
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