issue_comments
5 rows where issue = 985162305 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Mypy errors with the last version of _typed_ops.pyi · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
918073632 | https://github.com/pydata/xarray/issues/5755#issuecomment-918073632 | https://api.github.com/repos/pydata/xarray/issues/5755 | IC_kwDOAMm_X842uLEg | benbovy 4160723 | 2021-09-13T10:53:16Z | 2021-09-13T10:53:16Z | MEMBER | Thank you very much @max-sixty and @Illviljan for looking into this and for the PR! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mypy errors with the last version of _typed_ops.pyi 985162305 | |
910464045 | https://github.com/pydata/xarray/issues/5755#issuecomment-910464045 | https://api.github.com/repos/pydata/xarray/issues/5755 | IC_kwDOAMm_X842RJQt | Illviljan 14371165 | 2021-09-01T16:45:47Z | 2021-09-01T17:08:14Z | MEMBER | Before T_Dataset etc. was: https://github.com/pydata/xarray/blob/d58a5114ccc8656e83d8a31eebf720548f004f86/xarray/core/_typed_ops.pyi#L20-L22 This seems fixable by adding back https://github.com/pydata/xarray/blob/d58a5114ccc8656e83d8a31eebf720548f004f86/xarray/core/_typed_ops.pyi#L19-L22 What I wonder about is why we called it |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mypy errors with the last version of _typed_ops.pyi 985162305 | |
910480241 | https://github.com/pydata/xarray/issues/5755#issuecomment-910480241 | https://api.github.com/repos/pydata/xarray/issues/5755 | IC_kwDOAMm_X842RNNx | Illviljan 14371165 | 2021-09-01T17:05:57Z | 2021-09-01T17:05:57Z | MEMBER |
Agreed and maybe add a comment/TODO why it's called |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mypy errors with the last version of _typed_ops.pyi 985162305 | |
910467901 | https://github.com/pydata/xarray/issues/5755#issuecomment-910467901 | https://api.github.com/repos/pydata/xarray/issues/5755 | IC_kwDOAMm_X842RKM9 | max-sixty 5635139 | 2021-09-01T16:50:56Z | 2021-09-01T16:50:56Z | MEMBER |
The goal was for the type that's used throughout Xarray to be called Should we change that back, and change the mypy file files definition to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mypy errors with the last version of _typed_ops.pyi 985162305 | |
910464246 | https://github.com/pydata/xarray/issues/5755#issuecomment-910464246 | https://api.github.com/repos/pydata/xarray/issues/5755 | IC_kwDOAMm_X842RJT2 | max-sixty 5635139 | 2021-09-01T16:46:03Z | 2021-09-01T16:47:01Z | MEMBER | Edit: @Illviljan and I commented at the same time, he seems to have found the error! Great spot @benbovy . I think what's happening is that the standard run only checks ref https://github.com/pre-commit/mirrors-mypy/issues/33 for the pre-commit issue. On the errors themselves — @rhkleijn I think I have upset your magnum opus despite the best of intentions. If you're up for having a look, that would be great. Otherwise we could try and revert my original PR, though I worry this sort of refactor is difficult to revert. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mypy errors with the last version of _typed_ops.pyi 985162305 |
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