issue_comments
1 row where author_association = "CONTRIBUTOR" and issue = 769348008 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Plotting in 2D with one non-dimension coordinate given behaves contrary to documentation and can cause cryptic ValueError · 1 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 747621248 | https://github.com/pydata/xarray/issues/4702#issuecomment-747621248 | https://api.github.com/repos/pydata/xarray/issues/4702 | MDEyOklzc3VlQ29tbWVudDc0NzYyMTI0OA== | stanwest 38358698 | 2020-12-17T18:35:13Z | 2020-12-17T18:35:13Z | CONTRIBUTOR |
Yes. I didn't readily see that I needed to specify both
I agree that, if xarray is going to guess, handling non-dimension coordinates would be an improvement. It might be specified to work only with 1-D coordinates and to do nothing for multi-dimensional coordinates. Alternatively, is it at all preferable to remove the guessing feature? Although the behavior has been present for years, I found mention of it in the documentation only in "What's New." The motivating use case in #1290 could have been addressed instead simply with |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Plotting in 2D with one non-dimension coordinate given behaves contrary to documentation and can cause cryptic ValueError 769348008 |
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