issue_comments
1 row where issue = 1391699976 and user = 32801740 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- .sel return errors when using floats for no apparent reason · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1263689036 | https://github.com/pydata/xarray/issues/7108#issuecomment-1263689036 | https://api.github.com/repos/pydata/xarray/issues/7108 | IC_kwDOAMm_X85LUl1M | rhkleijn 32801740 | 2022-09-30T15:01:42Z | 2022-09-30T15:01:42Z | CONTRIBUTOR | Pandas docs seem stricter than the implementation. From this snippet from pandas source code monotonicity is only required after My concern with checking first is that code like below will stop working (if I understand correctly). Is has unique but (alphabetically) unsorted coords (although its order may have meaning for the user). I regularly select a slice by specifying the labels corresponding to the first and last elements I want to extract. I would suggest in this case to just try while catching any
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.sel return errors when using floats for no apparent reason 1391699976 |
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