issue_comments
1 row where author_association = "CONTRIBUTOR" and issue = 976207971 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Setting item with loc and boolean mask fails · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
904597086 | https://github.com/pydata/xarray/issues/5727#issuecomment-904597086 | https://api.github.com/repos/pydata/xarray/issues/5727 | IC_kwDOAMm_X8416w5e | niowniow 5802846 | 2021-08-24T12:28:18Z | 2021-08-24T12:31:21Z | CONTRIBUTOR | Thank you! You are right. I guess based on the docs for Assigning values with indexing I assumed only Should we add an example how to perform masking this way to the docs? There are many examples about masking using different ways, but not this simple, intuitive way. Even now, it's not really clear to me why "boolean"-masking should only work with integer-indexing and not label-indexing. Given that the highlighted edit: probably the reason is to support label-based indexing for boolean coords?! |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Setting item with loc and boolean mask fails 976207971 |
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