issue_comments

Table actions

5 rows where issue = 130743212 and user = 1217238 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

  • shoyer · 5 ✖

issue 1

  • Allow empty result of numerical operations between DataArrays · 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
184521334 https://github.com/pydata/xarray/pull/741#issuecomment-184521334 https://api.github.com/repos/pydata/xarray/issues/741 MDEyOklzc3VlQ29tbWVudDE4NDUyMTMzNA== shoyer 1217238 2016-02-16T05:01:07Z 2016-02-16T05:01:07Z MEMBER

I'm probably going to call this an "enhancement" rather than a bug fix, but otherwise this looks good... I'll fix up the what's new page shortly.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Allow empty result of numerical operations between DataArrays 130743212
184517662 https://github.com/pydata/xarray/pull/741#issuecomment-184517662 https://api.github.com/repos/pydata/xarray/issues/741 MDEyOklzc3VlQ29tbWVudDE4NDUxNzY2Mg== shoyer 1217238 2016-02-16T04:52:55Z 2016-02-16T04:52:55Z MEMBER

OK, going to merge this...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Allow empty result of numerical operations between DataArrays 130743212
184485089 https://github.com/pydata/xarray/pull/741#issuecomment-184485089 https://api.github.com/repos/pydata/xarray/issues/741 MDEyOklzc3VlQ29tbWVudDE4NDQ4NTA4OQ== shoyer 1217238 2016-02-16T02:37:37Z 2016-02-16T02:37:37Z MEMBER

Still thinking about the fillna behavior... I agree, it's weird that ds.fillna({'missing_variable': 0}) works without raising an error.

I would say this is consistent with in-place arithmetic on Datasets (i.e., left alignment of variable names), but we actually don't allow that with different variables currently... probably because I wanted to avoid this headache :). I think I'll add a special case in to ensure that we raise an error if there are unexpected variables in the fillna argument.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Allow empty result of numerical operations between DataArrays 130743212
180156107 https://github.com/pydata/xarray/pull/741#issuecomment-180156107 https://api.github.com/repos/pydata/xarray/issues/741 MDEyOklzc3VlQ29tbWVudDE4MDE1NjEwNw== shoyer 1217238 2016-02-05T02:04:40Z 2016-02-05T02:04:40Z MEMBER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Allow empty result of numerical operations between DataArrays 130743212
178872178 https://github.com/pydata/xarray/pull/741#issuecomment-178872178 https://api.github.com/repos/pydata/xarray/issues/741 MDEyOklzc3VlQ29tbWVudDE3ODg3MjE3OA== shoyer 1217238 2016-02-02T22:48:01Z 2016-02-02T22:48:01Z MEMBER

Version.py gets created when you install xarray, e.g., when you run pip install -e . after running git clone.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Allow empty result of numerical operations between DataArrays 130743212

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