issue_comments
5 rows where issue = 631085856 and user = 44142765 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Document writing netcdf from xarray directly to S3 · 5 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1453906696 | https://github.com/pydata/xarray/issues/4122#issuecomment-1453906696 | https://api.github.com/repos/pydata/xarray/issues/4122 | IC_kwDOAMm_X85WqNsI | zoj613 44142765 | 2023-03-03T18:08:07Z | 2023-03-03T18:08:07Z | NONE | Based on the docs
It appears scipy engine is safe is one does not need to be bothered with specifying engines.By the way, what are the limitations of the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Document writing netcdf from xarray directly to S3 631085856 | |
| 1453897364 | https://github.com/pydata/xarray/issues/4122#issuecomment-1453897364 | https://api.github.com/repos/pydata/xarray/issues/4122 | IC_kwDOAMm_X85WqLaU | zoj613 44142765 | 2023-03-03T18:00:33Z | 2023-03-03T18:00:33Z | NONE | I never needed to specify an engine when writing, you only need it when reading the file. I use the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Document writing netcdf from xarray directly to S3 631085856 | |
| 1401040677 | https://github.com/pydata/xarray/issues/4122#issuecomment-1401040677 | https://api.github.com/repos/pydata/xarray/issues/4122 | IC_kwDOAMm_X85Tgi8l | zoj613 44142765 | 2023-01-23T21:49:46Z | 2023-01-23T21:52:29Z | NONE | What didn't work:
Changing the above to
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Document writing netcdf from xarray directly to S3 631085856 | |
| 1400564474 | https://github.com/pydata/xarray/issues/4122#issuecomment-1400564474 | https://api.github.com/repos/pydata/xarray/issues/4122 | IC_kwDOAMm_X85Teur6 | zoj613 44142765 | 2023-01-23T15:44:20Z | 2023-01-23T15:44:20Z | NONE |
Thanks, this actually worked for me. It seems as though initializing an s3 store using |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Document writing netcdf from xarray directly to S3 631085856 | |
| 1400519887 | https://github.com/pydata/xarray/issues/4122#issuecomment-1400519887 | https://api.github.com/repos/pydata/xarray/issues/4122 | IC_kwDOAMm_X85TejzP | zoj613 44142765 | 2023-01-23T15:16:21Z | 2023-01-23T15:16:21Z | NONE | Is there any reliable to use to write a xr.Dataset object as a netcdf file in 2023? I tried using the above approach with |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Document writing netcdf from xarray directly to S3 631085856 |
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