issue_comments

Table actions

2 rows where issue = 1637898633 and user = 42680748 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

  • Ockenfuss · 2 ✖

issue 1

  • Interpolate_na: Rework 'limit' argument documentation/implementation · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1555970164 https://github.com/pydata/xarray/issues/7665#issuecomment-1555970164 https://api.github.com/repos/pydata/xarray/issues/7665 IC_kwDOAMm_X85cvjh0 Ockenfuss 42680748 2023-05-20T18:44:53Z 2023-05-20T18:44:53Z CONTRIBUTOR

Do you have any thoughts on this?

I think with the following signature, the function will be backward compatible: interpolate_na(dim, method='linear', use_coordinate=True, limit=None, limit_direction='forward', limit_area=None, limit_use_coordinate=False, max_gap=None)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Interpolate_na: Rework 'limit' argument documentation/implementation 1637898633
1481534629 https://github.com/pydata/xarray/issues/7665#issuecomment-1481534629 https://api.github.com/repos/pydata/xarray/issues/7665 IC_kwDOAMm_X85YTmyl Ockenfuss 42680748 2023-03-23T16:47:57Z 2023-03-23T16:47:57Z CONTRIBUTOR

Two comments if the pandas arguments are introduced: * If the pandas arguments are introduced, one might raise the question, whether the max_gap argument of xarray is still necessary, since pandas does not have such an argument. However, if the user does not want any interpolation if a gap is bigger than a specified length, this is currently not possible with pandas (actually, the max_gap feature is requested by the pandas community since a long time: pandas-dev/pandas#12187 ) * Coordinate handling: Currently, limit is operating on indices, max_gap is operating on coordinates. Is there a deeper reason for this separation? Both operations limit the interpolation 'distance'. If not, similar to use_coordinates, one could introduce something like limit_use_coordinates. If True, limit as well as max_gap refer to numeric coordinates, otherwise to a linearly increasing index ([0,1,2,...]).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Interpolate_na: Rework 'limit' argument documentation/implementation 1637898633

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