home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

4 rows where issue = 708337538 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 3

  • kmuehlbauer 2
  • dcherian 1
  • johnomotani 1

author_association 2

  • MEMBER 3
  • CONTRIBUTOR 1

issue 1

  • workaround for file with variable and dimension having same name · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1002687639 https://github.com/pydata/xarray/issues/4456#issuecomment-1002687639 https://api.github.com/repos/pydata/xarray/issues/4456 IC_kwDOAMm_X847w8yX dcherian 2448579 2021-12-29T16:55:53Z 2021-12-29T16:55:53Z MEMBER

Closing as dupe of #2233. This should be fixed by the explicit indexes refactor.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  workaround for file with variable and dimension having same name 708337538
1000363857 https://github.com/pydata/xarray/issues/4456#issuecomment-1000363857 https://api.github.com/repos/pydata/xarray/issues/4456 IC_kwDOAMm_X847oFdR kmuehlbauer 5821660 2021-12-23T15:07:35Z 2021-12-23T15:07:35Z MEMBER

Thanks @johnomotani me neither. I wonder if xarray could just invent the same as netcdf4 did, prepending the variables internally with some prefix. But this might only get confusing.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  workaround for file with variable and dimension having same name 708337538
1000305491 https://github.com/pydata/xarray/issues/4456#issuecomment-1000305491 https://api.github.com/repos/pydata/xarray/issues/4456 IC_kwDOAMm_X847n3NT johnomotani 3958036 2021-12-23T13:28:20Z 2021-12-23T13:28:20Z CONTRIBUTOR

I didn't find any solution in xarray - I think I ended up just dropping the conflicting variable...

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  workaround for file with variable and dimension having same name 708337538
999521909 https://github.com/pydata/xarray/issues/4456#issuecomment-999521909 https://api.github.com/repos/pydata/xarray/issues/4456 IC_kwDOAMm_X847k351 kmuehlbauer 5821660 2021-12-22T11:56:57Z 2021-12-22T11:56:57Z MEMBER

Is there any news on that topic? Has something being implemented already, to solve that issue? I'm wondering if roundtripping might be possible at all. As those files are valid nc-files, shouldn't xarray be capable of handling them?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  workaround for file with variable and dimension having same name 708337538

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]);
Powered by Datasette · Queries took 14.528ms · About: xarray-datasette