issue_comments
7 rows where issue = 499196320 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Changing dtype on v0.13.0 causes Dataset attributes to be lost · 7 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
750934788 | https://github.com/pydata/xarray/issues/3348#issuecomment-750934788 | https://api.github.com/repos/pydata/xarray/issues/3348 | MDEyOklzc3VlQ29tbWVudDc1MDkzNDc4OA== | mathause 10194086 | 2020-12-24T17:47:34Z | 2020-12-24T17:47:34Z | MEMBER | Yes, this is fixed so I am closing. Thanks for noting @rhkleijn |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Changing dtype on v0.13.0 causes Dataset attributes to be lost 499196320 | |
750929476 | https://github.com/pydata/xarray/issues/3348#issuecomment-750929476 | https://api.github.com/repos/pydata/xarray/issues/3348 | MDEyOklzc3VlQ29tbWVudDc1MDkyOTQ3Ng== | rhkleijn 32801740 | 2020-12-24T17:12:15Z | 2020-12-24T17:12:15Z | CONTRIBUTOR |
Output 1
Output 2 ``` Original xr.DataArray attrs: {'at_str': 'at1_value', 'at_float': 123.0, 'at_int': 123} dtype: int64 After casting to int64: {'at_str': 'at1_value', 'at_float': 123.0, 'at_int': 123} After casting to int32: {'at_str': 'at1_value', 'at_float': 123.0, 'at_int': 123} After casting to float32: {'at_str': 'at1_value', 'at_float': 123.0, 'at_int': 123} Changing the np.array attrs: {'at_str': 'at1_value', 'at_float': 123.0, 'at_int': 123} dtype: float32 ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Changing dtype on v0.13.0 causes Dataset attributes to be lost 499196320 | |
586959508 | https://github.com/pydata/xarray/issues/3348#issuecomment-586959508 | https://api.github.com/repos/pydata/xarray/issues/3348 | MDEyOklzc3VlQ29tbWVudDU4Njk1OTUwOA== | davidggphy 37239554 | 2020-02-17T11:52:32Z | 2020-02-17T11:52:32Z | NONE | The problem is still there, as it is quite unexpected. I hacked it using .astype() directly in the np.array Test code```python import xarray as xr da = xr.DataArray( np.arange(56).reshape((7, 8)), coords={ 'x': list('abcdefg'), 'y': 10 * np.arange(8) }, dims=['x', 'y'], attrs={"at_str":"at1_value","at_float":123.,"at_int":123} ) print("Original xr.DataArray") print(f"attrs: {da.attrs}") print(f"dtype: {da.dtype}") print(f"\nAfter casting to int64: {da.astype(np.int64).attrs}" ) print(f"After casting to int32: {da.astype(np.int32).attrs}" ) print(f"After casting to float32: {da.astype(np.float32).attrs}") da.values = da.values.astype(np.float32) print("\nChanging the np.array") print(f"attrs: {da.attrs}") print(f"dtype: {da.dtype}") ``` Output:``` Original xr.DataArray attrs: {'at_str': 'at1_value', 'at_float': 123.0, 'at_int': 123} dtype: int64 After casting to int64: {} After casting to int32: {} After casting to float32: {} Changing the np.array attrs: {'at_str': 'at1_value', 'at_float': 123.0, 'at_int': 123} dtype: float32 ```
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Changing dtype on v0.13.0 causes Dataset attributes to be lost 499196320 | |
536118536 | https://github.com/pydata/xarray/issues/3348#issuecomment-536118536 | https://api.github.com/repos/pydata/xarray/issues/3348 | MDEyOklzc3VlQ29tbWVudDUzNjExODUzNg== | shoyer 1217238 | 2019-09-27T22:43:48Z | 2019-09-27T22:43:48Z | MEMBER | It's also not clear to me how this managed to change/break but I think we should consider it a bug. I agree that the right fix is to write an explicit |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Changing dtype on v0.13.0 causes Dataset attributes to be lost 499196320 | |
535999921 | https://github.com/pydata/xarray/issues/3348#issuecomment-535999921 | https://api.github.com/repos/pydata/xarray/issues/3348 | MDEyOklzc3VlQ29tbWVudDUzNTk5OTkyMQ== | max-sixty 5635139 | 2019-09-27T16:01:57Z | 2019-09-27T16:01:57Z | MEMBER |
Do we have a view that this should be |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Changing dtype on v0.13.0 causes Dataset attributes to be lost 499196320 | |
535981805 | https://github.com/pydata/xarray/issues/3348#issuecomment-535981805 | https://api.github.com/repos/pydata/xarray/issues/3348 | MDEyOklzc3VlQ29tbWVudDUzNTk4MTgwNQ== | dcherian 2448579 | 2019-09-27T15:13:32Z | 2019-09-27T15:13:32Z | MEMBER | I guess the simpler solution is to just add an |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Changing dtype on v0.13.0 causes Dataset attributes to be lost 499196320 | |
535979151 | https://github.com/pydata/xarray/issues/3348#issuecomment-535979151 | https://api.github.com/repos/pydata/xarray/issues/3348 | MDEyOklzc3VlQ29tbWVudDUzNTk3OTE1MQ== | dcherian 2448579 | 2019-09-27T15:06:47Z | 2019-09-27T15:06:47Z | MEMBER | Should we switch The more general solution for DataArrays is to finish up #2070 (see also #2049). @robbibt are you you up for doing this? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Changing dtype on v0.13.0 causes Dataset attributes to be lost 499196320 |
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 6