issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 252543868 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

These facets timed out: author_association

user 1

  • shoyer · 3 ✖

issue 1

  • Dataset.__repr__ computes dask variables · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
325416896 https://github.com/pydata/xarray/issues/1522#issuecomment-325416896 https://api.github.com/repos/pydata/xarray/issues/1522 MDEyOklzc3VlQ29tbWVudDMyNTQxNjg5Ng== shoyer 1217238 2017-08-28T17:18:41Z 2017-08-28T17:18:41Z MEMBER

Hmm. My guess (untested) is that ds.coords['z'] = ('z', data) may be creating a Variable object instead of an IndexVariable by mistake. I opened another issue for this one: #1533

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset.__repr__ computes dask variables 252543868
325405998 https://github.com/pydata/xarray/issues/1522#issuecomment-325405998 https://api.github.com/repos/pydata/xarray/issues/1522 MDEyOklzc3VlQ29tbWVudDMyNTQwNTk5OA== shoyer 1217238 2017-08-28T16:38:30Z 2017-08-28T16:38:30Z MEMBER

There is a separate problem where index coords are computed twice.

Index coordinates (i.e., IndexVariable) are supposed to be calculated once, when they are added to an xarray object.

If they are getting computed via as_variable in expand_variable_dicts (which is called from _get_priority_vars()) then something has already gone wrong.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset.__repr__ computes dask variables 252543868
324709347 https://github.com/pydata/xarray/issues/1522#issuecomment-324709347 https://api.github.com/repos/pydata/xarray/issues/1522 MDEyOklzc3VlQ29tbWVudDMyNDcwOTM0Nw== shoyer 1217238 2017-08-24T17:54:20Z 2017-08-24T17:54:20Z MEMBER

I think we should probably just print the placeholders for dask arrays in all cases. The current behavior should require calling a .preview() method of some sort.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset.__repr__ computes dask variables 252543868

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