issue_comments

Table actions

5 rows where author_association = "MEMBER", issue = 1368740629 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions

user 1

  • dcherian · 5 ✖

issue 1

  • Generalize handling of chunked array types · 5 ✖

author_association 1

  • MEMBER · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1553390072 https://github.com/pydata/xarray/pull/7019#issuecomment-1553390072 https://api.github.com/repos/pydata/xarray/issues/7019 IC_kwDOAMm_X85cltn4 dcherian 2448579 2023-05-18T17:34:01Z 2023-05-18T17:34:01Z MEMBER

Thanks @TomNicholas Big change!

 
{
    "total_count": 3,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 3,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generalize handling of chunked array types 1368740629
1502378655 https://github.com/pydata/xarray/pull/7019#issuecomment-1502378655 https://api.github.com/repos/pydata/xarray/issues/7019 IC_kwDOAMm_X85ZjHqf dcherian 2448579 2023-04-10T21:57:04Z 2023-04-10T21:57:04Z MEMBER

We could still achieve the goal of running cubed without dask by making normalize_chunks the responsibility of the chunkmanager

Seems OK to me.

The other option is to xfail the broken tests on old dask versions

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generalize handling of chunked array types 1368740629
1469955680 https://github.com/pydata/xarray/pull/7019#issuecomment-1469955680 https://api.github.com/repos/pydata/xarray/issues/7019 IC_kwDOAMm_X85Xnb5g dcherian 2448579 2023-03-15T12:54:09Z 2023-03-15T12:54:09Z MEMBER

dask_array_ops.rolling - uses functions from dask.array.overlap

This is unused, we use sliding_window_view now.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generalize handling of chunked array types 1368740629
1469232494 https://github.com/pydata/xarray/pull/7019#issuecomment-1469232494 https://api.github.com/repos/pydata/xarray/issues/7019 IC_kwDOAMm_X85XkrVu dcherian 2448579 2023-03-15T02:54:59Z 2023-03-15T02:54:59Z MEMBER

AttributeError: 'tuple' object has no attribute 'tuple'

This means you're indexing a LazilyIndexedArray with a tuple but you need to wrap that tuple in an Indexer object llke BasicIndexer, VectorizedIndexer etc..

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generalize handling of chunked array types 1368740629
1400867666 https://github.com/pydata/xarray/pull/7019#issuecomment-1400867666 https://api.github.com/repos/pydata/xarray/issues/7019 IC_kwDOAMm_X85Tf4tS dcherian 2448579 2023-01-23T19:29:06Z 2023-01-23T19:29:06Z MEMBER

ramba doesn't actually require explicit chunks to work

I suspect Arkouda is similar in that this is not a detail the user is expected to worry about. (cc @sdbachman)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Generalize handling of chunked array types 1368740629

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