issue_comments
4 rows where author_association = "CONTRIBUTOR" and issue = 956103236 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Duck array compatibility meeting · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 924108418 | https://github.com/pydata/xarray/issues/5648#issuecomment-924108418 | https://api.github.com/repos/pydata/xarray/issues/5648 | IC_kwDOAMm_X843FMaC | jacobtomlinson 1610850 | 2021-09-21T15:37:12Z | 2021-09-21T15:38:56Z | CONTRIBUTOR | I can be there! @jakirkham and @pentschev are also Dask maintainers so there should be good representation. |
{
"total_count": 1,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 1,
"rocket": 0,
"eyes": 0
} |
Duck array compatibility meeting 956103236 | |
| 890191588 | https://github.com/pydata/xarray/issues/5648#issuecomment-890191588 | https://api.github.com/repos/pydata/xarray/issues/5648 | IC_kwDOAMm_X841Dz7k | pentschev 4398246 | 2021-07-30T22:04:51Z | 2021-07-30T22:04:51Z | CONTRIBUTOR | I'm also happy to join the meeting. Thanks @TomNicholas for the initiative here and @jacobtomlinson for tagging me. |
{
"total_count": 1,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 1,
"rocket": 0,
"eyes": 0
} |
Duck array compatibility meeting 956103236 | |
| 890165626 | https://github.com/pydata/xarray/issues/5648#issuecomment-890165626 | https://api.github.com/repos/pydata/xarray/issues/5648 | IC_kwDOAMm_X841Dtl6 | jthielen 3460034 | 2021-07-30T21:34:32Z | 2021-07-30T21:41:41Z | CONTRIBUTOR | Count me in for the meeting! Here are a few suggestions about possible topics to add to the agenda (based on linked issues/discussions), if we can fit it all in:
Also, tagging a few other array type libraries and maintainers/contributors who may be interested (please ping the relevant folks if you know them):
(interesting side note is the first three of these are all ndarray subclasses right now...perhaps discussing the interplay between array subclassing and wrapping is in order too?) |
{
"total_count": 1,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 1,
"rocket": 0,
"eyes": 0
} |
Duck array compatibility meeting 956103236 | |
| 889909886 | https://github.com/pydata/xarray/issues/5648#issuecomment-889909886 | https://api.github.com/repos/pydata/xarray/issues/5648 | IC_kwDOAMm_X841CvJ- | jacobtomlinson 1610850 | 2021-07-30T13:55:56Z | 2021-07-30T13:55:56Z | CONTRIBUTOR | Happy to attend. It might also be useful to have @pentschev involved too. |
{
"total_count": 1,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 1,
"rocket": 0,
"eyes": 0
} |
Duck array compatibility meeting 956103236 |
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 3