home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "MEMBER", issue = 957131705 and user = 2190658 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

  • hameerabbasi · 3 ✖

issue 1

  • recent versions of sparse and dask seem to be incompatible with our tests · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
908625623 https://github.com/pydata/xarray/issues/5654#issuecomment-908625623 https://api.github.com/repos/pydata/xarray/issues/5654 IC_kwDOAMm_X842KIbX hameerabbasi 2190658 2021-08-30T19:27:15Z 2021-08-30T19:27:15Z MEMBER

Thank you guys for the amazing investigation into the issues here. 🤗

I was basically pinpointed at the issues from my point of view.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  recent versions of sparse and dask seem to be incompatible with our tests 957131705
908317984 https://github.com/pydata/xarray/issues/5654#issuecomment-908317984 https://api.github.com/repos/pydata/xarray/issues/5654 IC_kwDOAMm_X842I9Ug hameerabbasi 2190658 2021-08-30T12:55:16Z 2021-08-30T12:55:16Z MEMBER

I have fixed the reported issues and released version 0.13.0 with the fixes included.

{
    "total_count": 4,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 3,
    "rocket": 1,
    "eyes": 0
}
  recent versions of sparse and dask seem to be incompatible with our tests 957131705
906723769 https://github.com/pydata/xarray/issues/5654#issuecomment-906723769 https://api.github.com/repos/pydata/xarray/issues/5654 IC_kwDOAMm_X842C4G5 hameerabbasi 2190658 2021-08-26T20:33:39Z 2021-08-26T20:33:39Z MEMBER

Third and final issue is when numpy.broadcast_to is applied to the output of zeros_like:

```

import sparse

s = sparse.COO.from_numpy([0, 0, 1, 2])

np.broadcast_to(np.zeros_like(s.todense(), shape=()), (3, ))

array([0, 0, 0])

np.broadcast_to(np.zeros_like(s, shape=()), (3, ))

ValueError: The data length does not match the coordinates given.

len(data) = 0, but 3 coords specified.

```

This seems like a genuine bug, please file it on our tracker if possible.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  recent versions of sparse and dask seem to be incompatible with our tests 957131705

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