issue_comments

Table actions

4 rows where issue = 1562408536 and user = 14808389 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

  • keewis · 4 ✖

issue 1

  • Data linked from https://docs.xarray.dev/en/stable/examples/ROMS_ocean_model.html is unavaible · 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
1412396521 https://github.com/pydata/xarray/issues/7486#issuecomment-1412396521 https://api.github.com/repos/pydata/xarray/issues/7486 IC_kwDOAMm_X85UL3Xp keewis 14808389 2023-02-01T17:00:14Z 2023-02-01T17:00:14Z MEMBER

thanks, that makes sense to me. I think that rules out option 3, so now we only need to decide whether we remove only the data url or the entire section (personally, I would lean towards the latter).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Data linked from https://docs.xarray.dev/en/stable/examples/ROMS_ocean_model.html is unavaible 1562408536
1412214395 https://github.com/pydata/xarray/issues/7486#issuecomment-1412214395 https://api.github.com/repos/pydata/xarray/issues/7486 IC_kwDOAMm_X85ULK57 keewis 14808389 2023-02-01T15:07:15Z 2023-02-01T15:07:15Z MEMBER

1 is the status quo (minus the removal of the data server url): the cells are set to "raw", so they are not run. We don't want to hit the server during CI anyways, as hitting the server would slow down the docs build too much.

It seems like there's at least two people who tried to follow the subsetting (or otherwise play with the raw data), so the section does have some value. However, I don't know how this compares to the burden of maintaining it, especially since we don't run it in CI.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Data linked from https://docs.xarray.dev/en/stable/examples/ROMS_ocean_model.html is unavaible 1562408536
1409066939 https://github.com/pydata/xarray/issues/7486#issuecomment-1409066939 https://api.github.com/repos/pydata/xarray/issues/7486 IC_kwDOAMm_X85T_Ke7 keewis 14808389 2023-01-30T17:56:04Z 2023-01-30T17:56:04Z MEMBER

don't we do that already? As far as I can tell, the url is there to explain where we got the data from and what preprocessing was done. Unless I'm missing something?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Data linked from https://docs.xarray.dev/en/stable/examples/ROMS_ocean_model.html is unavaible 1562408536
1408703594 https://github.com/pydata/xarray/issues/7486#issuecomment-1408703594 https://api.github.com/repos/pydata/xarray/issues/7486 IC_kwDOAMm_X85T9xxq keewis 14808389 2023-01-30T14:17:55Z 2023-01-30T14:17:55Z MEMBER

the data server is out of our control, so we can't fix this ourselves, unfortunately.

We might be able to look for a different server for that model, but I don't know enough about the model to do that myself. Any ideas, @pydata/xarray?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Data linked from https://docs.xarray.dev/en/stable/examples/ROMS_ocean_model.html is unavaible 1562408536

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