issue_comments: 843138842
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/5329#issuecomment-843138842 | https://api.github.com/repos/pydata/xarray/issues/5329 | 843138842 | MDEyOklzc3VlQ29tbWVudDg0MzEzODg0Mg== | 9010180 | 2021-05-18T12:43:55Z | 2021-05-18T13:40:41Z | NONE | @aurghs Point taken, but in that case the In principle, though, I'd be OK with any selection of potential exceptions, as long as they're documented. The current practical problem for us (the xcube developers) is that the behaviour change from 0.17 to 0.18 means that we now have to audit our existing codebases for potential uncaught |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
894125618 |