home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "MEMBER" and issue = 464888388 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 2

  • shoyer 2
  • dcherian 1

issue 1

  • Suppress warnings and add test coverage · 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
509769833 https://github.com/pydata/xarray/pull/3087#issuecomment-509769833 https://api.github.com/repos/pydata/xarray/issues/3087 MDEyOklzc3VlQ29tbWVudDUwOTc2OTgzMw== shoyer 1217238 2019-07-09T19:12:19Z 2019-07-09T19:12:19Z MEMBER

I'm going to merge this shortly, and leave further clean-up for later.

{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Suppress warnings and add test coverage 464888388
509300142 https://github.com/pydata/xarray/pull/3087#issuecomment-509300142 https://api.github.com/repos/pydata/xarray/issues/3087 MDEyOklzc3VlQ29tbWVudDUwOTMwMDE0Mg== shoyer 1217238 2019-07-08T16:37:44Z 2019-07-08T16:37:44Z MEMBER

Yeah, I'm not quite sure how we want to handle the datetime64 with timezones warnings. Possibly we just want to silence them in our test suite, and enocourage users to explicitly cast their pandas data to a dtype supported by numpy before loading it into xarray. Doing that properly would require the equivalent of "re-raising" a warning.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Suppress warnings and add test coverage 464888388
509269968 https://github.com/pydata/xarray/pull/3087#issuecomment-509269968 https://api.github.com/repos/pydata/xarray/issues/3087 MDEyOklzc3VlQ29tbWVudDUwOTI2OTk2OA== dcherian 2448579 2019-07-08T15:19:34Z 2019-07-08T15:19:34Z MEMBER

I'm also seeing ``` xarray/core/dataset.py:3666 /home/deepak/work/python/xarray/xarray/core/dataset.py:3666: FutureWarning: Converting timezone-aware DatetimeArray to timezone-naive ndarray with 'datetime64[ns]' dtype. In the future, this will return an ndarray with 'object' dtype where each element is a 'pandas.Timestamp' with the correct 'tz'. To accept the future behavior, pass 'dtype=object'. To keep the old behavior, pass 'dtype="datetime64[ns]"'. data = np.asarray(series).reshape(shape)

/home/deepak/miniconda3/envs/dcpy/lib/python3.7/site-packages/pandas/core/apply.py:286 /home/deepak/miniconda3/envs/dcpy/lib/python3.7/site-packages/pandas/core/apply.py:286: FutureWarning: Converting timezone-aware DatetimeArray to timezone-naive ndarray with 'datetime64[ns]' dtype. In the future, this will return an ndarray with 'object' dtype where each element is a 'pandas.Timestamp' with the correct 'tz'. To accept the future behavior, pass 'dtype=object'. To keep the old behavior, pass 'dtype="datetime64[ns]"'. results[i] = self.f(v) ```

locally.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Suppress warnings and add test coverage 464888388

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]);
Powered by Datasette · Queries took 639.992ms · About: xarray-datasette