home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where author_association = "MEMBER", issue = 298854863 and user = 10050469 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • fmaussion · 2 ✖

issue 1

  • Use conda-forge netcdftime wherever netcdf4 was tested · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
367637016 https://github.com/pydata/xarray/pull/1933#issuecomment-367637016 https://api.github.com/repos/pydata/xarray/issues/1933 MDEyOklzc3VlQ29tbWVudDM2NzYzNzAxNg== fmaussion 10050469 2018-02-22T10:27:03Z 2018-02-22T10:27:03Z MEMBER

Agreed. Do you think I should include that here?

As you wish! It can wait until the netcdftime documentation is up and running (most important I guess)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Use conda-forge netcdftime wherever netcdf4 was tested  298854863
367368044 https://github.com/pydata/xarray/pull/1933#issuecomment-367368044 https://api.github.com/repos/pydata/xarray/issues/1933 MDEyOklzc3VlQ29tbWVudDM2NzM2ODA0NA== fmaussion 10050469 2018-02-21T15:42:01Z 2018-02-21T15:42:01Z MEMBER

Is it safe to do so? I.e. can it hide bugs in the current netCDF4 time handling?

Also I think after #1920 it would be good to have a bit more info in the documentation about why people should switch to netcdftime or not.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Use conda-forge netcdftime wherever netcdf4 was tested  298854863

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