issue_comments
4 rows where issue = 1327380960 and user = 2448579 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Avoid calling np.asarray on lazy indexing classes · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1484205746 | https://github.com/pydata/xarray/pull/6874#issuecomment-1484205746 | https://api.github.com/repos/pydata/xarray/issues/6874 | IC_kwDOAMm_X85Ydy6y | dcherian 2448579 | 2023-03-26T19:58:05Z | 2023-03-26T19:58:05Z | MEMBER | I'd like to merge this at the end of next week. It now has tests and should be backwards compatible with external backends. A good next step would be to finish up #7020 |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 1, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Avoid calling np.asarray on lazy indexing classes 1327380960 | |
1433777395 | https://github.com/pydata/xarray/pull/6874#issuecomment-1433777395 | https://api.github.com/repos/pydata/xarray/issues/6874 | IC_kwDOAMm_X85VdbTz | dcherian 2448579 | 2023-02-16T22:03:22Z | 2023-02-16T22:03:22Z | MEMBER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Avoid calling np.asarray on lazy indexing classes 1327380960 | |
1433629099 | https://github.com/pydata/xarray/pull/6874#issuecomment-1433629099 | https://api.github.com/repos/pydata/xarray/issues/6874 | IC_kwDOAMm_X85Vc3Gr | dcherian 2448579 | 2023-02-16T19:52:38Z | 2023-02-16T19:52:38Z | MEMBER | @Illviljan feel free to push any typing changes to this PR. I think that would really help clarify the interface. I tried adding a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Avoid calling np.asarray on lazy indexing classes 1327380960 | |
1385842347 | https://github.com/pydata/xarray/pull/6874#issuecomment-1385842347 | https://api.github.com/repos/pydata/xarray/issues/6874 | IC_kwDOAMm_X85Smkar | dcherian 2448579 | 2023-01-17T18:21:01Z | 2023-01-17T18:26:51Z | MEMBER | background(Moving the convo out of a comment for visibility) For reference, the code we would like is
problemSo far I have found two fail cases 1. Wrapping a backend array instance
I tried this by making 2. Wrapping an IndexingAdapter instanceThe other case is when how to proceed?@shoyer I'm not sure on how to proceed.
1. For BackendArrays we could wrap them in another lazy indexing class when the Variable is created so we don't break our backend entrypoint contract (that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Avoid calling np.asarray on lazy indexing classes 1327380960 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1