issue_comments
3 rows where author_association = "MEMBER", issue = 1307523148 and user = 6213168 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Passing a distributed.Future to the kwargs of apply_ufunc should resolve the future · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1280764797 | https://github.com/pydata/xarray/issues/6803#issuecomment-1280764797 | https://api.github.com/repos/pydata/xarray/issues/6803 | IC_kwDOAMm_X85MVut9 | crusaderky 6213168 | 2022-10-17T12:15:36Z | 2022-10-17T12:20:02Z | MEMBER |
I've opened https://github.com/dask/distributed/issues/7140 to simplify this. With it implemented, my snippet
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Passing a distributed.Future to the kwargs of apply_ufunc should resolve the future 1307523148 | |
1280746923 | https://github.com/pydata/xarray/issues/6803#issuecomment-1280746923 | https://api.github.com/repos/pydata/xarray/issues/6803 | IC_kwDOAMm_X85MVqWr | crusaderky 6213168 | 2022-10-17T12:01:17Z | 2022-10-17T12:01:17Z | MEMBER | Having said the above, your design is... contrived. There isn't, as of today, a straightforward way to scatter a local dask collection ( Workaround:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Passing a distributed.Future to the kwargs of apply_ufunc should resolve the future 1307523148 | |
1280729879 | https://github.com/pydata/xarray/issues/6803#issuecomment-1280729879 | https://api.github.com/repos/pydata/xarray/issues/6803 | IC_kwDOAMm_X85MVmMX | crusaderky 6213168 | 2022-10-17T11:45:31Z | 2022-10-17T11:45:31Z | MEMBER |
test_future is not a dask collection. It's a distributed.Future, which points to an arbitrary, opaque data blob that xarray has no means to know about. FWIW, I could reproduce the issue, where the future in the kwargs is not resolved to the data it points to as one would expect. Minimal reproducer: ```python import distributed import xarray client = distributed.Client(processes=False) x = xarray.DataArray([1, 2]).chunk() test_future = client.scatter("Hello World") def f(d, test): print(test) return d y = xarray.apply_ufunc(
f,
x,
dask='parallelized',
output_dtypes="float64",
kwargs={'test':test_future},
)
y.compute()
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Passing a distributed.Future to the kwargs of apply_ufunc should resolve the future 1307523148 |
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