issue_comments

Table actions

6 rows where user = 717735 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

  • betolink · 6 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
984936456 https://github.com/pydata/xarray/issues/1068#issuecomment-984936456 https://api.github.com/repos/pydata/xarray/issues/1068 IC_kwDOAMm_X846tPAI betolink 717735 2021-12-02T19:30:14Z 2021-12-05T02:28:04Z NONE

I'm happy to help! @rabernat, Makhan @virdi from NASA Langley just reminded me the other day that there is a forum for NASA Earthdata users with a direct line to the program managers and scientists that may be the best place to ask data related questions. I think you only need to register with EDL.

https://forum.earthdata.nasa.gov/

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 1
}
   Use xarray.open_dataset() for password-protected Opendap files 186169975
971142092 https://github.com/pydata/xarray/issues/1068#issuecomment-971142092 https://api.github.com/repos/pydata/xarray/issues/1068 IC_kwDOAMm_X8454nPM betolink 717735 2021-11-17T03:29:28Z 2021-11-17T03:29:28Z NONE

Quick update, MERRA2 worked as expected after accepting the EULA again. GPM_L3 redirects to an empty .dods file, I guess that's a bug. I'll ask the OpenDAP team tomorrow if they are aware of this behavior and what would be a workaround/solution.

 
{
    "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
968999559 https://github.com/pydata/xarray/issues/1068#issuecomment-968999559 https://api.github.com/repos/pydata/xarray/issues/1068 IC_kwDOAMm_X845wcKH betolink 717735 2021-11-15T15:04:37Z 2021-11-15T15:04:37Z NONE

I just asked on Slack about how to check for these changes (if at the end this issue is indeed related to an updated EULA) and unfortunately there is no way around it other than doing what Jan did(and still got the 302s). About feedback, yes there are channels but they are on a per-DAAC basis (cries). In this case that would be going to https://daac.gsfc.nasa.gov/ and clicking on the feedback button. I'll keep looking at this after the cloud hackathon today. 

{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Use xarray.open_dataset() for password-protected Opendap files 186169975
968986677 https://github.com/pydata/xarray/issues/1068#issuecomment-968986677 https://api.github.com/repos/pydata/xarray/issues/1068 IC_kwDOAMm_X845wZA1 betolink 717735 2021-11-15T14:51:28Z 2021-11-15T14:51:28Z NONE

Yeah, definitely not ideal. I'm going to test it again this evening with a new Earthdata user. I'll send you a binder link to a notebook to test it with both accounts.

 
{
    "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
966777432 https://github.com/pydata/xarray/issues/1068#issuecomment-966777432 https://api.github.com/repos/pydata/xarray/issues/1068 IC_kwDOAMm_X845n9pY betolink 717735 2021-11-12T02:49:59Z 2021-11-15T14:37:48Z NONE

Looks like the dataset got updated and when that happens NASA requires users to accept the end user license agreement (again). That's why the request ends up in a redirect. This EULA is also required the first time a user requests the data. Here are the instructions for accepting GESDISC EULA. https://disc.gsfc.nasa.gov/earthdata-login

After the GESDIC data archive app shows up in our authorized apps list the code above works like a charm. I'll ask to see if there is a way to automate this @rabernat @zjans 

{
    "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
966600850 https://github.com/pydata/xarray/issues/1068#issuecomment-966600850 https://api.github.com/repos/pydata/xarray/issues/1068 IC_kwDOAMm_X845nSiS betolink 717735 2021-11-11T20:24:33Z 2021-11-11T20:24:33Z NONE

This looks familiar. I'm going to take a look at this when I get home and will report back. @rabernat 

{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 1,
    "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]);