issue_comments
2 rows where user = 110313 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 437988119 | https://github.com/pydata/xarray/issues/1982#issuecomment-437988119 | https://api.github.com/repos/pydata/xarray/issues/1982 | MDEyOklzc3VlQ29tbWVudDQzNzk4ODExOQ== | Chiil 110313 | 2018-11-12T18:45:21Z | 2018-11-12T18:45:21Z | NONE | How about searching in the parent group until the root group is reached? As far as I can see it, this cannot cause any conflict. It would be really awesome to have this functionality. I really like to idea of nicely organizing NetCDF files while still having the full functionality of xarray at hand.
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
NetCDF coordinates in parent group is not used when reading sub group 304314787 | |
| 437856617 | https://github.com/pydata/xarray/issues/1982#issuecomment-437856617 | https://api.github.com/repos/pydata/xarray/issues/1982 | MDEyOklzc3VlQ29tbWVudDQzNzg1NjYxNw== | Chiil 110313 | 2018-11-12T12:09:55Z | 2018-11-12T12:09:55Z | NONE | The problem occurs with plotting as well. See the StackOverflow question that I posted a few days ago. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
NetCDF coordinates in parent group is not used when reading sub group 304314787 |
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