issue_comments
10 rows where author_association = "MEMBER" and issue = 684930038 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Set `allow_rechunk=True` in `apply_ufunc` · 10 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
683621673 | https://github.com/pydata/xarray/issues/4372#issuecomment-683621673 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY4MzYyMTY3Mw== | kmuehlbauer 5821660 | 2020-08-31T07:43:34Z | 2020-08-31T07:43:34Z | MEMBER | @dcherian @shoyer In #4392 I've tried to get around this bug. I found it easier to just catch the dask ValueError's and not add more code checks. I'll add more information in that PR. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 | |
682756591 | https://github.com/pydata/xarray/issues/4372#issuecomment-682756591 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY4Mjc1NjU5MQ== | dcherian 2448579 | 2020-08-28T15:52:03Z | 2020-08-28T15:52:03Z | MEMBER | So to maintain backward compatibility, we should add that same check
and set We could deprecate and remove this check in a couple of versions but I don't know if it's worth the effort... |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 | |
682337819 | https://github.com/pydata/xarray/issues/4372#issuecomment-682337819 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY4MjMzNzgxOQ== | kmuehlbauer 5821660 | 2020-08-28T05:45:25Z | 2020-08-28T05:45:25Z | MEMBER |
Trying to answer this from looking at the dask code.
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 | |
682335024 | https://github.com/pydata/xarray/issues/4372#issuecomment-682335024 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY4MjMzNTAyNA== | kmuehlbauer 5821660 | 2020-08-28T05:35:28Z | 2020-08-28T05:35:28Z | MEMBER | From the dask ```python """ allow_rechunk: Optional, bool, keyword only
""" ``` Current code handling in dask:
IIUTC, this not only rechunks non-core dimensions but also fixes core dimensions with more than one chunk. Would this be intended from the
Explicit That means setting |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 | |
682327998 | https://github.com/pydata/xarray/issues/4372#issuecomment-682327998 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY4MjMyNzk5OA== | kmuehlbauer 5821660 | 2020-08-28T05:09:19Z | 2020-08-28T05:09:19Z | MEMBER | @shoyer In this case: Should we warn the user, that data might be loaded into memory? Another questions are, why does this kwarg exist in dask and why do they not rechunk per default? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 | |
682310286 | https://github.com/pydata/xarray/issues/4372#issuecomment-682310286 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY4MjMxMDI4Ng== | shoyer 1217238 | 2020-08-28T03:54:19Z | 2020-08-28T03:54:19Z | MEMBER | Maybe we do want to set allow_rechunk=True? It seems that I was just mistaken about the current behavior. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 | |
681605223 | https://github.com/pydata/xarray/issues/4372#issuecomment-681605223 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY4MTYwNTIyMw== | kmuehlbauer 5821660 | 2020-08-27T06:13:03Z | 2020-08-27T06:13:03Z | MEMBER | One solution would be to catch this ValueError, issue a FutureWarning and add ```python def func(*arrays): import dask.array as da
``` I could make a PR out of this. The message wording can surely be improved. WDYT @dcherian and @shoyer? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 | |
680940858 | https://github.com/pydata/xarray/issues/4372#issuecomment-680940858 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY4MDk0MDg1OA== | dcherian 2448579 | 2020-08-26T15:10:05Z | 2020-08-26T15:10:05Z | MEMBER | Copying over that comment...
@shoyer could you please clarify what you meant? For example, this works with v0.16.0 but fails on master ``` python import operator import numpy as np import xarray as xr a = xr.DataArray(np.ones((10, 10)), dims=("a", "b")).chunk({"a": 2, "b": 1}) b = xr.DataArray(np.ones((10, 10)), dims=("a", "b")).chunk({"a": -1, "b": 4}) xr.apply_ufunc( operator.add, a, b, dask="parallelized", output_dtypes=[a.dtype], ).compute().equals(a.compute() + b.compute()) ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 | |
679691483 | https://github.com/pydata/xarray/issues/4372#issuecomment-679691483 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY3OTY5MTQ4Mw== | kmuehlbauer 5821660 | 2020-08-25T05:20:32Z | 2020-08-25T05:20:32Z | MEMBER | The behaviour changed in #4060 (commit https://github.com/pydata/xarray/commit/a7fb5a9fa1a2b829181ea9e4986b959f315350dd). Please see discussion with regard to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 | |
679337446 | https://github.com/pydata/xarray/issues/4372#issuecomment-679337446 | https://api.github.com/repos/pydata/xarray/issues/4372 | MDEyOklzc3VlQ29tbWVudDY3OTMzNzQ0Ng== | dcherian 2448579 | 2020-08-24T20:03:42Z | 2020-08-24T20:03:42Z | MEMBER | (this is causing downstream test failures: https://github.com/NCAR/pop-tools/pull/59; thanks @mnlevy1981) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set `allow_rechunk=True` in `apply_ufunc` 684930038 |
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 3