issue_comments

Table actions

5 rows where issue = 525685973 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: issue

user 1

  • keewis · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
556253608 https://github.com/pydata/xarray/pull/3550#issuecomment-556253608 https://api.github.com/repos/pydata/xarray/issues/3550 MDEyOklzc3VlQ29tbWVudDU1NjI1MzYwOA== keewis 14808389 2019-11-20T19:03:23Z 2019-11-20T19:03:23Z MEMBER

I'm not sure about the examples in the examples folder, I think those are real-world examples?

What I meant was examples like those in DataArray.integrate (source) that simply demonstrate how to use that function.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cov() and corr() - finalization 525685973
556005779 https://github.com/pydata/xarray/pull/3550#issuecomment-556005779 https://api.github.com/repos/pydata/xarray/issues/3550 MDEyOklzc3VlQ29tbWVudDU1NjAwNTc3OQ== keewis 14808389 2019-11-20T13:35:22Z 2019-11-20T13:35:22Z MEMBER

since the APIs of DataArray and Dataset are usually kept in sync as much as possible, it might be good to add the new methods to Dataset, too. This doesn't have to be in this PR, though, and I'd wait for confirmation first.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cov() and corr() - finalization 525685973
555997448 https://github.com/pydata/xarray/pull/3550#issuecomment-555997448 https://api.github.com/repos/pydata/xarray/issues/3550 MDEyOklzc3VlQ29tbWVudDU1NTk5NzQ0OA== keewis 14808389 2019-11-20T13:12:23Z 2019-11-20T13:27:03Z MEMBER

for the new commit, yes. The older commits could be rewritten if you don't like the other email address being public (I can guide you through the process if you want) but since PRs get squashed during the merge you don't have to.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cov() and corr() - finalization 525685973
556002336 https://github.com/pydata/xarray/pull/3550#issuecomment-556002336 https://api.github.com/repos/pydata/xarray/issues/3550 MDEyOklzc3VlQ29tbWVudDU1NjAwMjMzNg== keewis 14808389 2019-11-20T13:25:52Z 2019-11-20T13:25:52Z MEMBER

yes, whats-new.rst and api.rst will have to eventually be updated before the merge. Also, examples would be really good.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cov() and corr() - finalization 525685973
555982665 https://github.com/pydata/xarray/pull/3550#issuecomment-555982665 https://api.github.com/repos/pydata/xarray/issues/3550 MDEyOklzc3VlQ29tbWVudDU1NTk4MjY2NQ== keewis 14808389 2019-11-20T12:27:08Z 2019-11-20T12:27:08Z MEMBER

There seems to be a problem with your email address (github can't match it to your account). Does it match the one you used for signing up on github?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cov() and corr() - finalization 525685973

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);