issue_comments

Table actions

3 rows where issue = 258640421 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 · 3 ✖

issue 1

  • Potential error in apply_ufunc docstring for input_core_dims · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
335359252 https://github.com/pydata/xarray/issues/1577#issuecomment-335359252 https://api.github.com/repos/pydata/xarray/issues/1577 MDEyOklzc3VlQ29tbWVudDMzNTM1OTI1Mg== shoyer 1217238 2017-10-10T04:42:21Z 2017-10-10T04:42:21Z MEMBER

Fixed by #1517.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Potential error in apply_ufunc docstring for input_core_dims 258640421
330635899 https://github.com/pydata/xarray/issues/1577#issuecomment-330635899 https://api.github.com/repos/pydata/xarray/issues/1577 MDEyOklzc3VlQ29tbWVudDMzMDYzNTg5OQ== shoyer 1217238 2017-09-19T18:51:55Z 2017-09-19T18:51:55Z MEMBER

My understanding is that the "core dimensions" are moved to the end of each input, and then singleton axes are inserted to make them broadcastable in a numpy sense. Is that correct?

Yes, exactly.

Though perhaps we should actually insert non-singleton dimensions to make it easier to understand.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Potential error in apply_ufunc docstring for input_core_dims 258640421
330587191 https://github.com/pydata/xarray/issues/1577#issuecomment-330587191 https://api.github.com/repos/pydata/xarray/issues/1577 MDEyOklzc3VlQ29tbWVudDMzMDU4NzE5MQ== shoyer 1217238 2017-09-19T16:00:21Z 2017-09-19T16:00:21Z MEMBER

Yes, this was a typo. I noticed this the other day and fixed on one of my local branches -- it should definitely go in before we make this public API.

I'll see about clarifying the concept of "core dimensions". I think it makes sense once you read the numpy docs, but this should stand alone. It does really just mean "dimensions that shouldn't be used for broadcasting" but an example would probably help.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Potential error in apply_ufunc docstring for input_core_dims 258640421

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