issue_comments

Table actions

3 rows where issue = 1371769156 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

author_association 2

issue 1

  • Assigning with .loc indexing: implicit effect of dimension order? · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1463502178 https://github.com/pydata/xarray/issues/7030#issuecomment-1463502178 https://api.github.com/repos/pydata/xarray/issues/7030 IC_kwDOAMm_X85XO0Vi maarten-vandenberg 24587365 2023-03-10T09:14:37Z 2023-03-10T09:14:37Z NONE

I'd be happy to open a pull request, although I must admit I'm not very familiar with the internals of xarray. I hope it will help to clarify the issue and bring a potential solution closer

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Assigning with .loc indexing: implicit effect of dimension order? 1371769156
1460508021 https://github.com/pydata/xarray/issues/7030#issuecomment-1460508021 https://api.github.com/repos/pydata/xarray/issues/7030 IC_kwDOAMm_X85XDZV1 dcherian 2448579 2023-03-08T17:02:32Z 2023-03-08T17:02:32Z MEMBER

Thanks @maarten-vandenberg . It looks like you have made an important step toward solving the problem.

Do you have time to open a pull request fixing this issue? Even an incomplete one helps get us closer to a fix.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Assigning with .loc indexing: implicit effect of dimension order? 1371769156
1459925203 https://github.com/pydata/xarray/issues/7030#issuecomment-1459925203 https://api.github.com/repos/pydata/xarray/issues/7030 IC_kwDOAMm_X85XBLDT maarten-vandenberg 24587365 2023-03-08T10:07:05Z 2023-03-08T10:07:33Z NONE

We are experiencing the same issue (with xarray version 2022.3.0). After a bit of exploring it seems that in the Variable __setitem__ method, dimensions of the value get switched around. This leads to the behaviour observed in the examples above.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Assigning with .loc indexing: implicit effect of dimension order? 1371769156

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);