issue_comments

Table actions

3 rows where author_association = "NONE", issue = 578427969 and user = 2444231 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

  • pgierz · 3 ✖

issue 1

  • Custom Table when opening GRIB Files · 3 ✖

author_association 1

  • NONE · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
598035459 https://github.com/pydata/xarray/issues/3853#issuecomment-598035459 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5ODAzNTQ1OQ== pgierz 2444231 2020-03-12T06:57:01Z 2020-03-12T06:57:01Z NONE

Me too! Then we have a good test case :-)

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Custom Table when opening GRIB Files 578427969
598020815 https://github.com/pydata/xarray/issues/3853#issuecomment-598020815 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5ODAyMDgxNQ== pgierz 2444231 2020-03-12T05:59:51Z 2020-03-12T05:59:51Z NONE

I can have a look at implementing this. Might be a nice opportunity to actually contribute to some of the packages I use every day ;-)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Custom Table when opening GRIB Files 578427969
597491042 https://github.com/pydata/xarray/issues/3853#issuecomment-597491042 https://api.github.com/repos/pydata/xarray/issues/3853 MDEyOklzc3VlQ29tbWVudDU5NzQ5MTA0Mg== pgierz 2444231 2020-03-11T07:50:43Z 2020-03-11T07:50:43Z NONE

Apparently this is possible by setting an environmental variable: http://www.pyngl.ucar.edu/NioFormats.shtml#GRIB1-user-defined-parameter-tables

So, if I have my codetable at /path/to/codetab; I can set NIO_GRIB_PTABLE_PATH=/path/to/codetab. I'm honestly not too happy with this solution. Would it be possible to add something like backend_env to open_dataset; where I can specify environmental variables that are active during opening, and then restore the environment afterwards?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Custom Table when opening GRIB Files 578427969

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