issue_comments
3 rows where author_association = "MEMBER" and issue = 266320445 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Unicode strings unexpectedly transformed to byte strings upon `open_dataset` · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
339228857 | https://github.com/pydata/xarray/issues/1638#issuecomment-339228857 | https://api.github.com/repos/pydata/xarray/issues/1638 | MDEyOklzc3VlQ29tbWVudDMzOTIyODg1Nw== | shoyer 1217238 | 2017-10-25T06:32:35Z | 2017-10-25T06:32:35Z | MEMBER | Hmm. I'm not sure why h5netcdf was so much slower. I suspect the default engine you used might have been scipy, which we've noticed can be significantly faster in some cases. If you have time, I would be curious how well my branch in 1648 works using Please file a separate issue if you can put together example code that reproduces the lost coordinate issue. I would like to dig into this. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unicode strings unexpectedly transformed to byte strings upon `open_dataset` 266320445 | |
338367929 | https://github.com/pydata/xarray/issues/1638#issuecomment-338367929 | https://api.github.com/repos/pydata/xarray/issues/1638 | MDEyOklzc3VlQ29tbWVudDMzODM2NzkyOQ== | shoyer 1217238 | 2017-10-21T06:27:57Z | 2017-10-21T06:27:57Z | MEMBER | Reading over Unidata/netcdf-c#402, it seems like we should probably copy the handling of _Encoding from netcdf4-python (Unidata/netcdf4-python#665) to our scipy interface. That would solve our problem of faithfully round-tripping data. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unicode strings unexpectedly transformed to byte strings upon `open_dataset` 266320445 | |
337426817 | https://github.com/pydata/xarray/issues/1638#issuecomment-337426817 | https://api.github.com/repos/pydata/xarray/issues/1638 | MDEyOklzc3VlQ29tbWVudDMzNzQyNjgxNw== | shoyer 1217238 | 2017-10-18T00:54:04Z | 2017-10-18T00:54:04Z | MEMBER | Which backend are you using to save the data? Try explicitly setting
This looks like a bug of some sort -- not sure how that happened! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Unicode strings unexpectedly transformed to byte strings upon `open_dataset` 266320445 |
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 1