issue_comments
6 rows where author_association = "MEMBER", issue = 682040124 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- update the instructions in the contributing guide · 6 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
677502566 | https://github.com/pydata/xarray/pull/4355#issuecomment-677502566 | https://api.github.com/repos/pydata/xarray/issues/4355 | MDEyOklzc3VlQ29tbWVudDY3NzUwMjU2Ng== | keewis 14808389 | 2020-08-20T09:59:40Z | 2020-08-20T09:59:40Z | MEMBER | Just so we don't forget: do we have a place where we collect ideas for the restructuring of the docs? Or should I just open a tracking issue for this and put it into the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
update the instructions in the contributing guide 682040124 | |
676821998 | https://github.com/pydata/xarray/pull/4355#issuecomment-676821998 | https://api.github.com/repos/pydata/xarray/issues/4355 | MDEyOklzc3VlQ29tbWVudDY3NjgyMTk5OA== | keewis 14808389 | 2020-08-20T00:07:04Z | 2020-08-20T00:07:04Z | MEMBER | so I guess this is ready for review and merge? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
update the instructions in the contributing guide 682040124 | |
676817977 | https://github.com/pydata/xarray/pull/4355#issuecomment-676817977 | https://api.github.com/repos/pydata/xarray/issues/4355 | MDEyOklzc3VlQ29tbWVudDY3NjgxNzk3Nw== | keewis 14808389 | 2020-08-19T23:51:40Z | 2020-08-19T23:51:40Z | MEMBER | phew, it seems having support set a feature flag to not do shallow clones fixed that particular issue. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
update the instructions in the contributing guide 682040124 | |
676784625 | https://github.com/pydata/xarray/pull/4355#issuecomment-676784625 | https://api.github.com/repos/pydata/xarray/issues/4355 | MDEyOklzc3VlQ29tbWVudDY3Njc4NDYyNQ== | keewis 14808389 | 2020-08-19T22:39:29Z | 2020-08-19T22:39:29Z | MEMBER | okay, so it seems this happens because RTD only makes shallow copies, as soon as we call |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
update the instructions in the contributing guide 682040124 | |
676736067 | https://github.com/pydata/xarray/pull/4355#issuecomment-676736067 | https://api.github.com/repos/pydata/xarray/issues/4355 | MDEyOklzc3VlQ29tbWVudDY3NjczNjA2Nw== | keewis 14808389 | 2020-08-19T21:54:19Z | 2020-08-19T21:54:19Z | MEMBER | re contributing docs: would it be best to leave that to the planned docs overhaul? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
update the instructions in the contributing guide 682040124 | |
676735131 | https://github.com/pydata/xarray/pull/4355#issuecomment-676735131 | https://api.github.com/repos/pydata/xarray/issues/4355 | MDEyOklzc3VlQ29tbWVudDY3NjczNTEzMQ== | keewis 14808389 | 2020-08-19T21:52:28Z | 2020-08-19T21:52:28Z | MEMBER | ugh. It seems this is the same error as in #4130. This time I can reproduce it locally, though, so now I'm debugging. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
update the instructions in the contributing guide 682040124 |
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