issues
3 rows where repo = 13221727, state = "closed" and user = 4801430 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date)
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at ▲ | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
863332419 | MDU6SXNzdWU4NjMzMzI0MTk= | 5197 | allow you to raise error on missing zarr chunks with open_dataset/open_zarr | bolliger32 4801430 | closed | 0 | 1 | 2021-04-21T00:00:03Z | 2023-11-24T22:14:18Z | 2023-11-24T22:14:18Z | CONTRIBUTOR | Is your feature request related to a problem? Please describe. Currently if a zarr store has a missing chunk, it is treaded as all missing. This is an upstream functionality but one for which there may soon be a kwarg allowing you to instead raise an error in these instances (https://github.com/zarr-developers/zarr-python/pull/489). This is valuable in situations where you would like to distinguish intentional NaN data from I/O errors that caused you to not write some chunks. Here's an example of a problematic case in this situation (courtesy of @delgadom ):
This prints: ``` data read into xarray <xarray.DataArray 'myarr' (x: 2, y: 2)> array([[ 0., nan], [ 2., 3.]]) Coordinates: * x (x) int64 0 1 * y (y) int64 0 1 structure of zarr store myzarr.zarr: myarr x y myzarr.zarr/myarr: 0.0 0.1 1.0 1.1 myzarr.zarr/x: 0 myzarr.zarr/y: 0 remove a chunk rm myzarr.zarr/myarr/1.0 data read into xarray <xarray.DataArray 'myarr' (x: 2, y: 2)> array([[ 0., nan], [nan, 3.]]) Coordinates: * x (x) int64 0 1 * y (y) int64 0 1 ``` Describe the solution you'd like
I'm not sure where a kwarg to the |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/5197/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
not_planned | xarray 13221727 | issue | ||||||
540601428 | MDExOlB1bGxSZXF1ZXN0MzU1Mzg5MDMx | 3649 | allow incomplete hypercubes in combine_by_coords | bolliger32 4801430 | closed | 0 | 5 | 2019-12-19T22:08:11Z | 2019-12-24T13:46:29Z | 2019-12-24T13:46:29Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/3649 |
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3649/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | pull | |||||
540578460 | MDU6SXNzdWU1NDA1Nzg0NjA= | 3648 | combine_by_coords should allow for missing panels in hypercube | bolliger32 4801430 | closed | 0 | 0 | 2019-12-19T21:29:02Z | 2019-12-24T13:46:28Z | 2019-12-24T13:46:28Z | CONTRIBUTOR | MCVE Code Sample
Expected Output
Problem DescriptionCurrently, it throws the following error:
Output of
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3648/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issues] ( [id] INTEGER PRIMARY KEY, [node_id] TEXT, [number] INTEGER, [title] TEXT, [user] INTEGER REFERENCES [users]([id]), [state] TEXT, [locked] INTEGER, [assignee] INTEGER REFERENCES [users]([id]), [milestone] INTEGER REFERENCES [milestones]([id]), [comments] INTEGER, [created_at] TEXT, [updated_at] TEXT, [closed_at] TEXT, [author_association] TEXT, [active_lock_reason] TEXT, [draft] INTEGER, [pull_request] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [state_reason] TEXT, [repo] INTEGER REFERENCES [repos]([id]), [type] TEXT ); CREATE INDEX [idx_issues_repo] ON [issues] ([repo]); CREATE INDEX [idx_issues_milestone] ON [issues] ([milestone]); CREATE INDEX [idx_issues_assignee] ON [issues] ([assignee]); CREATE INDEX [idx_issues_user] ON [issues] ([user]);