issue_comments

Table actions

1 row where issue = 235224055 and user = 900941 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

  • guziy · 1 ✖

issue 1

  • time.units truncated when saving to_netcdf · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
786735133 https://github.com/pydata/xarray/issues/1449#issuecomment-786735133 https://api.github.com/repos/pydata/xarray/issues/1449 MDEyOklzc3VlQ29tbWVudDc4NjczNTEzMw== guziy 900941 2021-02-26T16:01:15Z 2021-02-26T16:46:33Z CONTRIBUTOR

Hi, I have a similar problem. We have model runs starting at 0Z and 12Z so the ones starting at 0Z don't have time (only date) in the unit string, which is not consistent... Is there a workaround?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   time.units truncated when saving to_netcdf 235224055

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