issue_comments

Table actions

1 row where author_association = "CONTRIBUTOR" and issue = 1367029446 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

issue 1

  • Time-based resampling drops lat/lon coordinate metadata · 1 ✖

author_association 1

  • CONTRIBUTOR · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1243917954 https://github.com/pydata/xarray/issues/7012#issuecomment-1243917954 https://api.github.com/repos/pydata/xarray/issues/7012 IC_kwDOAMm_X85KJK6C Zeitsperre 10819524 2022-09-12T15:33:10Z 2022-09-12T15:33:10Z CONTRIBUTOR

@mathause You're right! I noticed this first in my builds using "upstream" dependencies (xarray@main, flox@main, cftime@master, bottleneck@master). It might indeed be flox-related!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Time-based resampling drops lat/lon coordinate metadata 1367029446

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