issue_comments
3 rows where issue = 222676855 and user = 500246 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Many methods are broken (e.g., concat/stack/sortby) when using repeated dimensions · 3 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 376106248 | https://github.com/pydata/xarray/issues/1378#issuecomment-376106248 | https://api.github.com/repos/pydata/xarray/issues/1378 | MDEyOklzc3VlQ29tbWVudDM3NjEwNjI0OA== | gerritholl 500246 | 2018-03-26T09:38:00Z | 2018-03-26T09:38:00Z | CONTRIBUTOR | This also affects the |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Many methods are broken (e.g., concat/stack/sortby) when using repeated dimensions 222676855 | |
| 367153633 | https://github.com/pydata/xarray/issues/1378#issuecomment-367153633 | https://api.github.com/repos/pydata/xarray/issues/1378 | MDEyOklzc3VlQ29tbWVudDM2NzE1MzYzMw== | gerritholl 500246 | 2018-02-20T23:10:13Z | 2018-02-20T23:10:13Z | CONTRIBUTOR | @jhamman Ok, good to hear it's not slated to be removed. I would love to work on this, I wish I had the time! I'll keep it in mind if I do find some spare time. |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Many methods are broken (e.g., concat/stack/sortby) when using repeated dimensions 222676855 | |
| 367147759 | https://github.com/pydata/xarray/issues/1378#issuecomment-367147759 | https://api.github.com/repos/pydata/xarray/issues/1378 | MDEyOklzc3VlQ29tbWVudDM2NzE0Nzc1OQ== | gerritholl 500246 | 2018-02-20T22:46:27Z | 2018-02-20T22:46:27Z | CONTRIBUTOR |
I use repeated dimensions to store a covariance matrix. The data variable containing the covariance matrix has 4 dimensions, of which the last 2 are repeated. For example, I have a data variable with dimensions ( This is valid NetCDF and should be valid in xarray. It would be a significant problem for me if they became disallowed. |
{
"total_count": 6,
"+1": 6,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Many methods are broken (e.g., concat/stack/sortby) when using repeated dimensions 222676855 |
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