issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 663968779 and user = 226037 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

  • alexamici · 3 ✖

issue 1

  • [community] Backends refactor meeting · 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
780682558 https://github.com/pydata/xarray/issues/4253#issuecomment-780682558 https://api.github.com/repos/pydata/xarray/issues/4253 MDEyOklzc3VlQ29tbWVudDc4MDY4MjU1OA== alexamici 226037 2021-02-17T16:33:31Z 2021-02-17T16:33:31Z MEMBER

@jhamman & @shoyer, unfortunately neither @aurghs nor myself will be available tomorrow, 18 Feb. We can skip this week's meeting or reschedule it, same time but another day. Your call.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [community] Backends refactor meeting 663968779
683350819 https://github.com/pydata/xarray/issues/4253#issuecomment-683350819 https://api.github.com/repos/pydata/xarray/issues/4253 MDEyOklzc3VlQ29tbWVudDY4MzM1MDgxOQ== alexamici 226037 2020-08-29T23:00:52Z 2020-08-29T23:00:52Z MEMBER

So weekly meeting every Thurday, perfect (cc @aurghs @TheRed86)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [community] Backends refactor meeting 663968779
680842271 https://github.com/pydata/xarray/issues/4253#issuecomment-680842271 https://api.github.com/repos/pydata/xarray/issues/4253 MDEyOklzc3VlQ29tbWVudDY4MDg0MjI3MQ== alexamici 226037 2020-08-26T12:15:02Z 2020-08-26T12:15:02Z MEMBER

@shoyer every other Thursday at 8am Los Angeles time works for us in general, but not tomorrow when both @aurghs and myself already made arrangements, sorry!

We have been studying the details of indexing, that lead us to find an embarrassing bug in cfgrib https://github.com/ecmwf/cfgrib/issues/157, and we are now getting into write support.

I think we can do without this week meeting and we will sync on the regular community meeting.

Feel free to set up regular meeting starting next week of in two weeks (alternating with the community meeting seem the easiest).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [community] Backends refactor meeting 663968779

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