issue_comments

Table actions

4 rows where issue = 146079798 and user = 2443309 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

  • jhamman · 4 ✖

issue 1

  • modified: xarray/backends/api.py · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1411179632 https://github.com/pydata/xarray/pull/817#issuecomment-1411179632 https://api.github.com/repos/pydata/xarray/issues/817 IC_kwDOAMm_X85UHORw jhamman 2443309 2023-01-31T22:51:57Z 2023-01-31T22:51:57Z MEMBER

Closing this as stale and out of date with our current backends. @swnesbitt (or others) - feel free to open a new PR if you feel there is more to do here.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   modified: xarray/backends/api.py 146079798
388412798 https://github.com/pydata/xarray/pull/817#issuecomment-388412798 https://api.github.com/repos/pydata/xarray/issues/817 MDEyOklzc3VlQ29tbWVudDM4ODQxMjc5OA== jhamman 2443309 2018-05-11T16:20:26Z 2018-05-11T16:20:26Z MEMBER

@tsaoyu - I don't think anyone has worked on developing a test case for this feature. I assume @swnesbitt would appreciate help there. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   modified: xarray/backends/api.py 146079798
218359192 https://github.com/pydata/xarray/pull/817#issuecomment-218359192 https://api.github.com/repos/pydata/xarray/issues/817 MDEyOklzc3VlQ29tbWVudDIxODM1OTE5Mg== jhamman 2443309 2016-05-11T04:31:46Z 2016-05-11T04:31:46Z MEMBER

@shoyer - are we okay with the final logic here?

@swnesbitt - can we get an entry in the what's new docs?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   modified: xarray/backends/api.py 146079798
206464547 https://github.com/pydata/xarray/pull/817#issuecomment-206464547 https://api.github.com/repos/pydata/xarray/issues/817 MDEyOklzc3VlQ29tbWVudDIwNjQ2NDU0Nw== jhamman 2443309 2016-04-06T16:59:58Z 2016-04-06T16:59:58Z MEMBER

Regarding testing, it would be good to have a test module that includes grabbing files for local access and accessing openDAP datasets (from UNIDATA?) to ensure that the installed backends are all working as expected.

I'd be a little hesitant to enforce that we get access to opendap (or other remote datasets) on travis. I've seen this come back to bite us in the past. We can allow tests to fail on travis and just print a warning via pytest if it is something we really want to see tested in that way.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   modified: xarray/backends/api.py 146079798

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