issue_comments
5 rows where author_association = "NONE" and user = 2086210 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- brianmapes · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1258874354 | https://github.com/pydata/xarray/issues/4240#issuecomment-1258874354 | https://api.github.com/repos/pydata/xarray/issues/4240 | IC_kwDOAMm_X85LCOXy | brianmapes 2086210 | 2022-09-27T02:14:28Z | 2022-09-27T02:14:28Z | NONE | +1 Complicated, still vexing this user a year+ later, but it easier for me to just restart the kernel again and again than read this and #4879, which is closed but didn't seem to have succeeded if I read correctly? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
jupyter repr caching deleted netcdf file 662505658 | |
1062281975 | https://github.com/pydata/xarray/issues/1613#issuecomment-1062281975 | https://api.github.com/repos/pydata/xarray/issues/1613 | IC_kwDOAMm_X84_USL3 | brianmapes 2086210 | 2022-03-08T22:26:07Z | 2022-03-08T22:26:07Z | NONE | Agreed, new rather than redefine existing meanings. Who has the chops and the cred to implement it? Not quite me... |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Should sel with slice objects care about underlying coordinate order? 263403430 | |
1062142845 | https://github.com/pydata/xarray/issues/1613#issuecomment-1062142845 | https://api.github.com/repos/pydata/xarray/issues/1613 | IC_kwDOAMm_X84_TwN9 | brianmapes 2086210 | 2022-03-08T19:49:33Z | 2022-03-08T19:49:33Z | NONE | How about an informative warning when returning an empty set, as a minimal change? What's the path to an action item here? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Should sel with slice objects care about underlying coordinate order? 263403430 | |
1058446923 | https://github.com/pydata/xarray/issues/1613#issuecomment-1058446923 | https://api.github.com/repos/pydata/xarray/issues/1613 | IC_kwDOAMm_X84_Fp5L | brianmapes 2086210 | 2022-03-03T20:19:56Z | 2022-03-03T20:19:56Z | NONE | @shoyer, New syntax like your first suggestion, |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Should sel with slice objects care about underlying coordinate order? 263403430 | |
1058341139 | https://github.com/pydata/xarray/issues/1613#issuecomment-1058341139 | https://api.github.com/repos/pydata/xarray/issues/1613 | IC_kwDOAMm_X84_FQET | brianmapes 2086210 | 2022-03-03T18:13:31Z | 2022-03-03T20:03:15Z | NONE | How about: add one code line at the top of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Should sel with slice objects care about underlying coordinate order? 263403430 |
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]);
issue 2