issue_comments

Table actions

1 row where issue = 1039113959 and user = 316517 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

  • astrojuanlu · 1 ✖

issue 1

  • Invalid characters in OpenDAP URL · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1458897500 https://github.com/pydata/xarray/issues/5913#issuecomment-1458897500 https://api.github.com/repos/pydata/xarray/issues/5913 IC_kwDOAMm_X85W9QJc astrojuanlu 316517 2023-03-07T21:27:13Z 2023-03-07T21:27:13Z NONE

We had the exact same issue (I'm using an old version of xarray, netCDF4, and Hyrax because I'm running an old app). I'm not sure when things broke, but what we ended up doing was configuring Tomcat to allow square brackets as advised in the mailing list thread posted by OP. We unfortunately don't have much time to debug this issue or add more info, but I hope this is useful for folks arriving here from search engines (as I did).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Invalid characters in OpenDAP URL 1039113959

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