issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 290244473 and user = 10050469 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1

  • fmaussion · 1 ✖

issue 1

  • Add a suite of property-based tests with Hypothesis · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
374583416 https://github.com/pydata/xarray/issues/1846#issuecomment-374583416 https://api.github.com/repos/pydata/xarray/issues/1846 MDEyOklzc3VlQ29tbWVudDM3NDU4MzQxNg== fmaussion 10050469 2018-03-20T12:42:21Z 2018-03-20T12:42:21Z MEMBER

Reopening this issue as there is still a list of possible TODOs, as per @shoyer comment:

  • [ ] Consistency with pandas for groupby/rolling aggregations.
  • [ ] Roundtrip writing/reading data to netCDF. There are a couple of known exceptions (e.g., dtypes not supported by netCDF and MultiIndex) but otherwise every xarray object should be serializable to netCDF and back without data loss.
  • [ ] Roundtrip to/from pandas Series/DataFrame with to_series()/to_dataframe()/to_xarray().
  • [ ] Indexing consistency tests for backends: all indexing operations should be supported consistently on data accessed from any backend.
  • [ ] NumPy vs Dask: any operation on dask arrays should be consistent with the operation on numpy arrays (e.g., f(xarray_obj.chunk()).compute() == f(xarray_obj)).
  • [ ] Indexing followed by xarray.concat: should get back the same result.
  • [ ] Binary arithmetic on xarray objects with Python operators (+, -, etc) and NumPy ufuncs (np.add, np.subtract, etc).
 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add a suite of property-based tests with Hypothesis 290244473

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