issue_comments
4 rows where author_association = "NONE" and issue = 304314787 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- NetCDF coordinates in parent group is not used when reading sub group · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
612137754 | https://github.com/pydata/xarray/issues/1982#issuecomment-612137754 | https://api.github.com/repos/pydata/xarray/issues/1982 | MDEyOklzc3VlQ29tbWVudDYxMjEzNzc1NA== | lamorton 23484003 | 2020-04-10T17:38:50Z | 2020-04-10T17:38:50Z | NONE | I'm currently working around this by loading the root group & the branch group with two separate calls and then merging the resulting datasets. It's ugly b/c I have to manually associate the 'phony_dim_x' dimensions from one group with the other. Maybe I can find the time during quarantine to make an attempt at resolving #1092, which I think would facilitate resolving this issue as well. Another option would be to allow the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
NetCDF coordinates in parent group is not used when reading sub group 304314787 | |
437988119 | https://github.com/pydata/xarray/issues/1982#issuecomment-437988119 | https://api.github.com/repos/pydata/xarray/issues/1982 | MDEyOklzc3VlQ29tbWVudDQzNzk4ODExOQ== | Chiil 110313 | 2018-11-12T18:45:21Z | 2018-11-12T18:45:21Z | NONE | How about searching in the parent group until the root group is reached? As far as I can see it, this cannot cause any conflict. It would be really awesome to have this functionality. I really like to idea of nicely organizing NetCDF files while still having the full functionality of xarray at hand.
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
NetCDF coordinates in parent group is not used when reading sub group 304314787 | |
437856617 | https://github.com/pydata/xarray/issues/1982#issuecomment-437856617 | https://api.github.com/repos/pydata/xarray/issues/1982 | MDEyOklzc3VlQ29tbWVudDQzNzg1NjYxNw== | Chiil 110313 | 2018-11-12T12:09:55Z | 2018-11-12T12:09:55Z | NONE | The problem occurs with plotting as well. See the StackOverflow question that I posted a few days ago. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
NetCDF coordinates in parent group is not used when reading sub group 304314787 | |
372324699 | https://github.com/pydata/xarray/issues/1982#issuecomment-372324699 | https://api.github.com/repos/pydata/xarray/issues/1982 | MDEyOklzc3VlQ29tbWVudDM3MjMyNDY5OQ== | jacklovell 4849151 | 2018-03-12T14:17:01Z | 2018-03-12T14:17:01Z | NONE | It looks to me like #1092 is about a Dataset-like object which can contain groups and sub-groups. Here we have a simpler issue: the Dataset can still be a flat object containing a single group, but it should respect the scope of netCDF dimensions. This means that any dimensions which are mentioned but not visible in the group being written should be searched for and copied (linked?) from a parent group, up to and including the root group if the dimensions reside there. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
NetCDF coordinates in parent group is not used when reading sub group 304314787 |
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