issue_comments
4 rows where author_association = "MEMBER" and issue = 731681563 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Alternative way to deal scale_factor and add_offset for opening datasets. · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 719592753 | https://github.com/pydata/xarray/issues/4548#issuecomment-719592753 | https://api.github.com/repos/pydata/xarray/issues/4548 | MDEyOklzc3VlQ29tbWVudDcxOTU5Mjc1Mw== | kmuehlbauer 5821660 | 2020-10-30T14:41:32Z | 2020-10-30T14:41:32Z | MEMBER | @nbCloud91 Nice! That's what I had mind. The loop should not be that much of an issue. Thanks for coming back and thanks for the code snippet. Hope those who come here find it useful. |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Alternative way to deal scale_factor and add_offset for opening datasets. 731681563 | |
| 719541192 | https://github.com/pydata/xarray/issues/4548#issuecomment-719541192 | https://api.github.com/repos/pydata/xarray/issues/4548 | MDEyOklzc3VlQ29tbWVudDcxOTU0MTE5Mg== | kmuehlbauer 5821660 | 2020-10-30T13:06:52Z | 2020-10-30T13:06:52Z | MEMBER | @nbCloud91 Can you point me to the relevant SO-question? And did my sparse answer help you in any way? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Alternative way to deal scale_factor and add_offset for opening datasets. 731681563 | |
| 718947729 | https://github.com/pydata/xarray/issues/4548#issuecomment-718947729 | https://api.github.com/repos/pydata/xarray/issues/4548 | MDEyOklzc3VlQ29tbWVudDcxODk0NzcyOQ== | kmuehlbauer 5821660 | 2020-10-29T18:42:19Z | 2020-10-29T18:42:19Z | MEMBER | @nbCloud91 I would do the same as you opening |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Alternative way to deal scale_factor and add_offset for opening datasets. 731681563 | |
| 718884875 | https://github.com/pydata/xarray/issues/4548#issuecomment-718884875 | https://api.github.com/repos/pydata/xarray/issues/4548 | MDEyOklzc3VlQ29tbWVudDcxODg4NDg3NQ== | kmuehlbauer 5821660 | 2020-10-29T16:53:15Z | 2020-10-29T16:53:15Z | MEMBER | @nbCloud91 What do you mean by manually doing the scaling? It seems that for your case it would be enough to fix the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Alternative way to deal scale_factor and add_offset for opening datasets. 731681563 |
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