home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where issue = 102416901 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

  • shoyer 1
  • spencerkclark 1
  • stale[bot] 1

author_association 2

  • MEMBER 2
  • NONE 1

issue 1

  • Negative timesteps after .to_netcdf with long time periods? · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
459569502 https://github.com/pydata/xarray/issues/545#issuecomment-459569502 https://api.github.com/repos/pydata/xarray/issues/545 MDEyOklzc3VlQ29tbWVudDQ1OTU2OTUwMg== spencerkclark 6628425 2019-02-01T01:15:22Z 2019-02-01T01:15:22Z MEMBER

This is the same issue as #2272, which was fixed in #2519.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Negative timesteps after .to_netcdf with long time periods? 102416901
459555242 https://github.com/pydata/xarray/issues/545#issuecomment-459555242 https://api.github.com/repos/pydata/xarray/issues/545 MDEyOklzc3VlQ29tbWVudDQ1OTU1NTI0Mg== stale[bot] 26384082 2019-02-01T00:05:49Z 2019-02-01T00:05:49Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here; otherwise it will be marked as closed automatically

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Negative timesteps after .to_netcdf with long time periods? 102416901
133511952 https://github.com/pydata/xarray/issues/545#issuecomment-133511952 https://api.github.com/repos/pydata/xarray/issues/545 MDEyOklzc3VlQ29tbWVudDEzMzUxMTk1Mg== shoyer 1217238 2015-08-21T17:53:52Z 2015-08-21T17:53:52Z MEMBER

This looks like some sort of integer overflow bug. Oddly, the times actually roundtrips fine back into xray (but probably not other programs that read netCDFs).

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Negative timesteps after .to_netcdf with long time periods? 102416901

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 4000.459ms · About: xarray-datasette