issue_comments
4 rows where author_association = "MEMBER" and issue = 272415954 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Error when using engine='scipy' reading CM2.6 ocean output · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
456593474 | https://github.com/pydata/xarray/issues/1704#issuecomment-456593474 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDQ1NjU5MzQ3NA== | dcherian 2448579 | 2019-01-22T22:48:21Z | 2019-01-22T22:48:21Z | MEMBER | Closing in favour of #1823 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 | |
345919689 | https://github.com/pydata/xarray/issues/1704#issuecomment-345919689 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDM0NTkxOTY4OQ== | jhamman 2443309 | 2017-11-21T05:17:14Z | 2017-11-21T05:17:14Z | MEMBER | @jbusecke -
In your case, what would that have looked like? Many users have actually requested that xarray provide a more streamlined reader function that does less checking. Perhaps it would have been useful for you to have xarray raise an error when it encountered files that weren't consistent (either in the variable, dimensions, or coordinates)? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 | |
343352694 | https://github.com/pydata/xarray/issues/1704#issuecomment-343352694 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDM0MzM1MjY5NA== | shoyer 1217238 | 2017-11-10T02:02:51Z | 2017-11-10T02:02:51Z | MEMBER | Can you figure out which variable name it's erroring on? Try dropping into a debugger (e.g., It is not immediately obvious to me what the issue is with this file, but I suspect this is probably a SciPy issue given that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 | |
343030828 | https://github.com/pydata/xarray/issues/1704#issuecomment-343030828 | https://api.github.com/repos/pydata/xarray/issues/1704 | MDEyOklzc3VlQ29tbWVudDM0MzAzMDgyOA== | shoyer 1217238 | 2017-11-09T02:46:09Z | 2017-11-09T02:46:09Z | MEMBER | Can you share an example file? Note that there are some performance improvements for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Error when using engine='scipy' reading CM2.6 ocean output 272415954 |
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