issue_comments

Table actions

3 rows where issue = 186169975 and user = 3217406 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • laliberte · 3 ✖

issue 1

  • Use xarray.open_dataset() for password-protected Opendap files · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
305775273 https://github.com/pydata/xarray/issues/1068#issuecomment-305775273 https://api.github.com/repos/pydata/xarray/issues/1068 MDEyOklzc3VlQ29tbWVudDMwNTc3NTI3Mw== laliberte 3217406 2017-06-02T12:44:23Z 2017-06-02T13:00:46Z CONTRIBUTOR

@jenfly and @shoyer pydap version 3.2.2 (newly released last week) should have fixed this issue. Could you verify?

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Use xarray.open_dataset() for password-protected Opendap files 186169975
291262663 https://github.com/pydata/xarray/issues/1068#issuecomment-291262663 https://api.github.com/repos/pydata/xarray/issues/1068 MDEyOklzc3VlQ29tbWVudDI5MTI2MjY2Mw== laliberte 3217406 2017-04-03T20:24:07Z 2017-04-03T20:24:07Z CONTRIBUTOR

@shoyer @jenfly: Good news, I think I was able to track down the bug in pydap that was preventing compatibility. I'm putting a PR together and we could expect it to be merged pretty soon into the master. I wanted to give you a heads up so that you don't waste more time on this.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Use xarray.open_dataset() for password-protected Opendap files 186169975
290189772 https://github.com/pydata/xarray/issues/1068#issuecomment-290189772 https://api.github.com/repos/pydata/xarray/issues/1068 MDEyOklzc3VlQ29tbWVudDI5MDE4OTc3Mg== laliberte 3217406 2017-03-29T18:54:09Z 2017-03-29T18:54:09Z CONTRIBUTOR

I like the idea of passing PydapDataStore objects that include the session object. It seems more likely to be forward compatible, especially if Central Authentication Services multiply (as one would expect) with different authentication mechanisms.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Use xarray.open_dataset() for password-protected Opendap files 186169975

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