issue_comments
1 row where issue = 321917084 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: author_association
issue 1
- Rolling mean of dask array conflicting sizes for data and coordinate in rolling operation · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
388099066 | https://github.com/pydata/xarray/issues/2113#issuecomment-388099066 | https://api.github.com/repos/pydata/xarray/issues/2113 | MDEyOklzc3VlQ29tbWVudDM4ODA5OTA2Ng== | shoyer 1217238 | 2018-05-10T16:00:12Z | 2018-05-10T16:00:12Z | MEMBER | @raybellwaves thanks for the bug report! Here's a slightly simplified version that shows the issue for dask: ``` import pandas as pd import xarray as xr import numpy as np da_day_clim = xr.DataArray(np.arange(1, 367), coords=[np.arange(1, 367)], dims='dayofyear') print(da_day_clim.rolling(dayofyear=31, center=True).mean()) # works print(da_day_clim.chunk().rolling(dayofyear=31, center=True).mean()) # raises ValueError ``` The traceback is probably the place to start looking into this. I like to drop into a Python debugger (type |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rolling mean of dask array conflicting sizes for data and coordinate in rolling operation 321917084 |
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