home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where user = 20627856 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 2

  • Non-HTTPS remote URLs no longer work as input for open_zarr 2
  • Allow fsspec URLs in open_(mf)dataset 1

user 1

  • charlesbluca · 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
787394145 https://github.com/pydata/xarray/issues/4691#issuecomment-787394145 https://api.github.com/repos/pydata/xarray/issues/4691 MDEyOklzc3VlQ29tbWVudDc4NzM5NDE0NQ== charlesbluca 20627856 2021-02-28T04:48:52Z 2021-02-28T04:48:52Z NONE

With @martindurant's PR merged, this should be fixed now - thanks!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Non-HTTPS remote URLs no longer work as input for open_zarr 766826777
762490131 https://github.com/pydata/xarray/pull/4823#issuecomment-762490131 https://api.github.com/repos/pydata/xarray/issues/4823 MDEyOklzc3VlQ29tbWVudDc2MjQ5MDEzMQ== charlesbluca 20627856 2021-01-18T22:05:52Z 2021-01-18T22:05:52Z NONE

Looking over the changes to is_remote_uri(), it looks like this should resolve the issue I had at #4691!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Allow fsspec URLs in open_(mf)dataset 788398518
761648598 https://github.com/pydata/xarray/issues/4691#issuecomment-761648598 https://api.github.com/repos/pydata/xarray/issues/4691 MDEyOklzc3VlQ29tbWVudDc2MTY0ODU5OA== charlesbluca 20627856 2021-01-16T20:54:19Z 2021-01-16T20:54:19Z NONE

Good to know - I figured this issue would be covered in that PR.

In general, I tend to use fsspec.get_mapper() in all cases where I need to access a remote store, but figured this would be good to document as it could potentially result in xarray workflows breaking with the version bump - for example, this PR in cmip6_preprocessing was the reason I opened this issue, as it showcases a Zarr testing suite that worked on 0.16.1 and stopped working on 0.16.2.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Non-HTTPS remote URLs no longer work as input for open_zarr 766826777

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.04ms · About: xarray-datasette