issue_comments
1 row where issue = 1415592761 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- combine_by_coords allows one overlapping coordinate value, but not more than one · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1285855378 | https://github.com/pydata/xarray/issues/7189#issuecomment-1285855378 | https://api.github.com/repos/pydata/xarray/issues/7189 | IC_kwDOAMm_X85MpJiS | TomNicholas 35968931 | 2022-10-20T16:40:56Z | 2022-10-20T16:40:56Z | MEMBER | Thanks so much for the MVCE, sleuthing, and clear issue @mjwillson !
That sounds likely to me.
Definitely not intentional. I'm not sure this case even occurred to me when I originally wrote
I hope not too because it's sort of an undefined operation. The purpose of We do also state clearly in the docstring "
A PR would be most welcome :smile: We should also consider the behaviour in the case of repeated elements in the coordinates, e.g. this currently happens:
Alternatively we might consider first changing the code to raise a warning if the resulting coordinate is monotonic but non-unique, so that when we change the actual behaviour later people are ready.
That sounds sensible. As an aside, I wonder if we could create a hypothesis test for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
combine_by_coords allows one overlapping coordinate value, but not more than one 1415592761 |
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