issue_comments
3 rows where author_association = "CONTRIBUTOR", issue = 1293460108 and user = 21131639 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- MultiIndex listed multiple times in Dataset.indexes property · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1236917784 | https://github.com/pydata/xarray/issues/6752#issuecomment-1236917784 | https://api.github.com/repos/pydata/xarray/issues/6752 | IC_kwDOAMm_X85Jud4Y | lukasbindreiter 21131639 | 2022-09-05T12:07:13Z | 2022-09-05T12:07:13Z | CONTRIBUTOR | Thanks for the suggestions, I'll look into this And with regards to the (de)serialization: I haven't investigated yet how the As for the original issue discussed here: That can probably be closed then, since it was an intentional change.
But finding information about those changes right now was not so easy, is there some resource available where I can read up about the changes to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
MultiIndex listed multiple times in Dataset.indexes property 1293460108 | |
1236717180 | https://github.com/pydata/xarray/issues/6752#issuecomment-1236717180 | https://api.github.com/repos/pydata/xarray/issues/6752 | IC_kwDOAMm_X85Jts58 | lukasbindreiter 21131639 | 2022-09-05T08:51:24Z | 2022-09-05T08:51:24Z | CONTRIBUTOR | @benbovy I also just tested the Taking the above dataset ```python
TypeError: unhashable type: 'MultiIndex' ``` However, for
[<xarray.core.indexes.PandasMultiIndex at 0x7f105bf1df20>] ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
MultiIndex listed multiple times in Dataset.indexes property 1293460108 | |
1236714136 | https://github.com/pydata/xarray/issues/6752#issuecomment-1236714136 | https://api.github.com/repos/pydata/xarray/issues/6752 | IC_kwDOAMm_X85JtsKY | lukasbindreiter 21131639 | 2022-09-05T08:48:23Z | 2022-09-05T08:48:23Z | CONTRIBUTOR | We used the Saving dataset as NetCDF:
1. Loop over And then loading it again: 1. Load the dataset 2. Check if this special attribute exists 3. If so decode the multiindex and set it as index in the dataset When testing the pre-release version I noticed some of our tests failing, which is why I raised this issue in the first place - in case those changes were unwanted. I was not aware that you were actively working on multi index changes and therefore expecting API changes here. With that in mind I'll probably be able to adapt our code to this new API of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
MultiIndex listed multiple times in Dataset.indexes property 1293460108 |
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