issue_comments

Table actions

1 row where issue = 252490115 and user = 6980561 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • klapo · 1 ✖

issue 1

  • Assignment · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
604543399 https://github.com/pydata/xarray/issues/1519#issuecomment-604543399 https://api.github.com/repos/pydata/xarray/issues/1519 MDEyOklzc3VlQ29tbWVudDYwNDU0MzM5OQ== klapo 6980561 2020-03-26T16:50:44Z 2020-03-26T16:50:44Z NONE

I'm re-pinging this issue since I was just bitten by it (on version 0.15).

If creating an exception is time consuming could we instead have a disclaimer regarding this behavior to the documentation? Here's a basic working example that shows that it does silently fail:

```

Basic working example of the silently failing indexing assignment

ds = xr.Dataset({'a': (('x'), np.arange(4)), 'b': (('x'), np.arange(4)) })

Silently fails assignment

ds.loc[{'x': 1}]['a'] = 10 print(ds)

Works as intended

ds['a'].loc[{'x': 1}] = 10 print(ds) ```

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Assignment 252490115

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