issue_comments

Table actions

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

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • shoyer · 3 ✖

issue 1

  • Problem with creating coords by dict · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
326144658 https://github.com/pydata/xarray/issues/1197#issuecomment-326144658 https://api.github.com/repos/pydata/xarray/issues/1197 MDEyOklzc3VlQ29tbWVudDMyNjE0NDY1OA== shoyer 1217238 2017-08-30T23:12:59Z 2017-08-30T23:12:59Z MEMBER

Do we still want to deprecate this behavior in v0.10?

Sure, that seems reasonable to me.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Problem with creating coords by dict 199816142
271928169 https://github.com/pydata/xarray/issues/1197#issuecomment-271928169 https://api.github.com/repos/pydata/xarray/issues/1197 MDEyOklzc3VlQ29tbWVudDI3MTkyODE2OQ== shoyer 1217238 2017-01-11T17:07:23Z 2017-01-11T17:07:23Z MEMBER

@SpghttCd Yes, I was confused. I missed that you were writing np.zeros, so reply doesn't make much sense!

On master (and in the next release of xarray), we do indeed issue a warning here as @fmaussion points out. Unfortunately, we did support this behavior in prior releases of xarray (especially with an OrderedDict), so I think we should keep the deprecation warning around for a while before making this behavior an error (probably in v0.10).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Problem with creating coords by dict 199816142
271715645 https://github.com/pydata/xarray/issues/1197#issuecomment-271715645 https://api.github.com/repos/pydata/xarray/issues/1197 MDEyOklzc3VlQ29tbWVudDI3MTcxNTY0NQ== shoyer 1217238 2017-01-10T22:16:33Z 2017-01-10T22:16:33Z MEMBER

You shouldn't be able to make a DataArray like this -- you have three dimensions on coordinates, but only one dimension on the array itself.

With xarray 0.8.2, you get an error message with your example: import xarray as xr arr = xr.DataArray(np.zeros([1, 2, 3]), {'x': [1], 'y': [1, 2], 'z': [1, 2, 3]}) ValueError: conflicting sizes for dimension 'z': length 1 on the data but length 3 on coordinate 'z' However, this error message is not quite accurate. You need to explicitly provide dims to get a sensible error: arr = xr.DataArray(np.zeros([1, 2, 3]), {'x': [1], 'y': [1, 2], 'z': [1, 2, 3]}, dims=['x']) ValueError: coordinate z has dimensions ('z',), but these are not a subset of the DataArray dimensions ['x']

I still need to test this on the dev version, but for now I will make this as an error reporting bug.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Problem with creating coords by dict 199816142

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