issue_comments

Table actions

1 row where issue = 685739084 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

issue 1

  • allow using non-dimension coordinates in polyfit · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
696845767 https://github.com/pydata/xarray/issues/4375#issuecomment-696845767 https://api.github.com/repos/pydata/xarray/issues/4375 MDEyOklzc3VlQ29tbWVudDY5Njg0NTc2Nw== aulemahal 20629530 2020-09-22T16:50:26Z 2020-09-22T16:50:26Z CONTRIBUTOR

I did encounter this when writing up polyfit! I decided to discard that for the time being, but I believe changing get_clean_interp_index would the best way to fix this. One would also need to modify polyfit sligthly, though. Here: https://github.com/pydata/xarray/blob/9c85dd5f792805bea319f01f08ee51b83bde0f3b/xarray/core/dataset.py#L6064-L6075 When the non-fitted dimensions are stacked together, dim should be renamed to the real dimension of the variable. I will not have time to make a PR, but it should be quite simple, if anyone has time!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   allow using non-dimension coordinates in polyfit 685739084

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);