issue_comments
2 rows where issue = 911513701 and user = 31376402 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- bug or unclear definition of combine_attrs with xr.merge() · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
872210975 | https://github.com/pydata/xarray/issues/5436#issuecomment-872210975 | https://api.github.com/repos/pydata/xarray/issues/5436 | MDEyOklzc3VlQ29tbWVudDg3MjIxMDk3NQ== | caenrigen 31376402 | 2021-07-01T12:37:52Z | 2021-07-01T12:37:52Z | CONTRIBUTOR | @keewis thank you for the reply
Does this mean that my workaround is not fully working as I would like it to? (I want it to basically do nothing to the attrs) Is it possible at the moment to pass |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
bug or unclear definition of combine_attrs with xr.merge() 911513701 | |
871681764 | https://github.com/pydata/xarray/issues/5436#issuecomment-871681764 | https://api.github.com/repos/pydata/xarray/issues/5436 | MDEyOklzc3VlQ29tbWVudDg3MTY4MTc2NA== | caenrigen 31376402 | 2021-06-30T19:49:24Z | 2021-06-30T19:49:24Z | CONTRIBUTOR | Hey guys! First of all thank you for the work on maintaining this package 😃 I am running into the same issue and it is partially blocking an open-source package (used in experimental quantum computing) from adopting the latest version of xarray. For our typical dataset this happens:
As default behavior this is totally unexpected because the variables attributes have nothing to do with the dataset itself. I am just trying to put all my data in a single container. (Am i using the wrong function for this?) And second, My suggestion is to do nothing by default, i.e. I understand there might be cases where combining the attributes makes sense, so maybe my suggestion only applies when only Hope my use case helps this discussion. In the meantime the workaround seems to be:
```bash <xarray.Dataset> Dimensions: (dim_0: 5) Dimensions without coordinates: dim_0 Data variables: x0 (dim_0) float64 1.0 1.0 1.0 1.0 1.0 y0 (dim_0) float64 1.0 1.0 1.0 1.0 1.0 === <xarray.DataArray 'x0' (dim_0: 5)> array([1., 1., 1., 1., 1.]) Dimensions without coordinates: dim_0 Attributes: name: x long_name: X position units: m batched: False ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
bug or unclear definition of combine_attrs with xr.merge() 911513701 |
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