home / github / pull_requests

Menu
  • GraphQL API
  • Search all tables

pull_requests: 313308718

This data as json

id node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association auto_merge repo url merged_by
313308718 MDExOlB1bGxSZXF1ZXN0MzEzMzA4NzE4 3276 closed 0 map_blocks 2448579 <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] xref #3147, closes #3323 - [x] Tests added - [x] Passes `black . && mypy . && flake8` - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API This is a second attempt. It works with Datasets also in that it can pass Dataset chunks to the user's function. I haven't figured out how to reconstruct a Dataset from things returned from the user's function. For DataArrays, I currently assume that the user function returns chunks of the same shape as the provided chunk. A few questions: 1. I wonder if we should introduce a meta xarray object that describes the final result that user expects back i.e. a template DataArray or Dataset with chunks, dtype etc. specified. We could have a utility function that makes it easy to create these templates from existing objects. 2. If the user function doesn't return anything, (e.g. it writes to a file), how do I "compute" the graph? In this case, we could rename this function to `apply_blocks` and release that till we figure out point 1? 3. Should we also add `Dataset.to_delayed` and `DataArray.to_delayed`? This would make use-cases like the one in point 2 easier. ping @mrocklin 2019-09-02T15:32:42Z 2019-10-17T01:30:30Z 2019-10-10T23:44:19Z 2019-10-10T23:44:19Z 3f295511acdf4e2c6a6bdf7bcbba5be519d45e9b     0 2a41906970ae720bcad04c0b7abd60655ac7fb5f 291cb805bf0bf326da87152cc6548191bbeb6aab MEMBER   13221727 https://github.com/pydata/xarray/pull/3276  

Links from other tables

  • 0 rows from pull_requests_id in labels_pull_requests
Powered by Datasette · Queries took 0.65ms