issue_comments

Table actions

4 rows where issue = 97237275 and user = 358378 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • andreas-h · 4 ✖

issue 1

  • ENH: finite difference method `diff` · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
133003335 https://github.com/pydata/xarray/pull/495#issuecomment-133003335 https://api.github.com/repos/pydata/xarray/issues/495 MDEyOklzc3VlQ29tbWVudDEzMzAwMzMzNQ== andreas-h 358378 2015-08-20T13:11:49Z 2015-08-20T13:11:49Z CONTRIBUTOR

That's strange, I cannot reproduce the test failure on my system ... Any ideas?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: finite difference method `diff` 97237275
125250524 https://github.com/pydata/xarray/pull/495#issuecomment-125250524 https://api.github.com/repos/pydata/xarray/issues/495 MDEyOklzc3VlQ29tbWVudDEyNTI1MDUyNA== andreas-h 358378 2015-07-27T15:47:17Z 2015-07-27T15:47:17Z CONTRIBUTOR

I'm not really happy with my implementation; the coordinate/variable handling in lines 1870-1884 are far from elegant. But is there a nicer way to do this?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: finite difference method `diff` 97237275
125244483 https://github.com/pydata/xarray/pull/495#issuecomment-125244483 https://api.github.com/repos/pydata/xarray/issues/495 MDEyOklzc3VlQ29tbWVudDEyNTI0NDQ4Mw== andreas-h 358378 2015-07-27T15:27:48Z 2015-07-27T15:27:48Z CONTRIBUTOR

I wouldn't allow full control here, but maybe a keyword argument for choosing whether to take the "lower", "upper" or "mean" labels would be appropriate.

I don't see how 'mean' could work, as the coord might be of dtype str. But I'm implementing 'upper' and 'lower'. If the user wants something different, she can always just swap the coord manually.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: finite difference method `diff` 97237275
124862963 https://github.com/pydata/xarray/pull/495#issuecomment-124862963 https://api.github.com/repos/pydata/xarray/issues/495 MDEyOklzc3VlQ29tbWVudDEyNDg2Mjk2Mw== andreas-h 358378 2015-07-25T17:15:10Z 2015-07-25T17:15:10Z CONTRIBUTOR

Actually, the current implementation leads to 0.0 for arrays inside a Dataset which don't have dim as a dimension. I personally would find it more intuitive if those arrays would not be touched at all.

Do you agree, or do you prefer this 0.0 for unaffected arrays?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ENH: finite difference method `diff` 97237275

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