issue_comments
4 rows where issue = 809853736 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- memoryview is too large saving 1.77GB Array · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 781514156 | https://github.com/pydata/xarray/issues/4918#issuecomment-781514156 | https://api.github.com/repos/pydata/xarray/issues/4918 | MDEyOklzc3VlQ29tbWVudDc4MTUxNDE1Ng== | conaghili 68662648 | 2021-02-18T17:35:45Z | 2021-02-18T17:35:45Z | NONE | upon looking around I needed to use June_ULCVarXr.load() before to_netcdf(). I think it was trying to use dask to write. So to make sure I tried .load(). Apparently it worked |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
memoryview is too large saving 1.77GB Array 809853736 | |
| 781487143 | https://github.com/pydata/xarray/issues/4918#issuecomment-781487143 | https://api.github.com/repos/pydata/xarray/issues/4918 | MDEyOklzc3VlQ29tbWVudDc4MTQ4NzE0Mw== | conaghili 68662648 | 2021-02-18T16:56:12Z | 2021-02-18T16:57:16Z | NONE | So I tested saving a file without running it through dask
Maybe it was trying to use dask to write the file???? I'm going to rerun the code with .load() before to_netcdf to see if that helps |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
memoryview is too large saving 1.77GB Array 809853736 | |
| 780934253 | https://github.com/pydata/xarray/issues/4918#issuecomment-780934253 | https://api.github.com/repos/pydata/xarray/issues/4918 | MDEyOklzc3VlQ29tbWVudDc4MDkzNDI1Mw== | conaghili 68662648 | 2021-02-17T23:59:49Z | 2021-02-18T00:01:31Z | NONE |
The computer the data is stored on is undergoing maintenance tonight -- I'll get on it tomorrow morning to check! I'm more or less trying a way to handle large data and would love to solve this output error since if I get it working this would be a method I'd use on a lot of extremely large netcdfs moving forward |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
memoryview is too large saving 1.77GB Array 809853736 | |
| 780926683 | https://github.com/pydata/xarray/issues/4918#issuecomment-780926683 | https://api.github.com/repos/pydata/xarray/issues/4918 | MDEyOklzc3VlQ29tbWVudDc4MDkyNjY4Mw== | mathause 10194086 | 2021-02-17T23:41:11Z | 2021-02-17T23:41:11Z | MEMBER | The error does not tell me anything, could you try to open the data also with xarray. You'll need to do something along the lines of
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
memoryview is too large saving 1.77GB Array 809853736 |
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 2