issue_comments: 1170900930
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/6733#issuecomment-1170900930 | https://api.github.com/repos/pydata/xarray/issues/6733 | 1170900930 | IC_kwDOAMm_X85FyofC | 9569132 | 2022-06-30T08:05:47Z | 2022-06-30T08:05:47Z | NONE | Thanks @dcherian - completely agree that assuming 65535 is a fill can be confusing. My question is basically solved, but the big memory increase is surprising to me. If you cast first, when required, you still have the user data at the original precision as a reference for the filling step? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1286995366 |