issue_comments: 459177873
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/pull/2706#issuecomment-459177873 | https://api.github.com/repos/pydata/xarray/issues/2706 | 459177873 | MDEyOklzc3VlQ29tbWVudDQ1OTE3Nzg3Mw== | 1197350 | 2019-01-31T01:24:11Z | 2019-01-31T01:24:11Z | MEMBER | So the problem in @davidbrochart's example is that there are different encodings on the time variables in the two datasets. When writing datetimes, xarray automatically picks an encoding (i.e. In this case, xarray's heuristics are picking different encodings for the two dates. You could make this example work by manually specifying encoding on the appended dataset to be the same as the original. This example illustrates the need for some sort of compatibility checks between the target dataset and the appended dataset. For example, checking for attribute compatibility would have caught this error. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
402908148 |