issue_comments

Table actions

5 rows where issue = 1281386064 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 1

  • ⚠️ Nightly upstream-dev CI failed ⚠️ · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1176365361 https://github.com/pydata/xarray/issues/6716#issuecomment-1176365361 https://api.github.com/repos/pydata/xarray/issues/6716 IC_kwDOAMm_X85GHekx dcherian 2448579 2022-07-06T15:29:47Z 2022-07-06T15:29:55Z MEMBER

Should be fixed on upstream pandas: https://github.com/pandas-dev/pandas/pull/47367

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ⚠️ Nightly upstream-dev CI failed ⚠️ 1281386064
1164514510 https://github.com/pydata/xarray/issues/6716#issuecomment-1164514510 https://api.github.com/repos/pydata/xarray/issues/6716 IC_kwDOAMm_X85FaRTO dcherian 2448579 2022-06-23T14:56:07Z 2022-06-23T14:56:33Z MEMBER

@keewis yes that's it! I saw it on flox and thought some default changed and hope they would fix it :)

We definitely depend on the default creating non-overlapping intervals.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ⚠️ Nightly upstream-dev CI failed ⚠️ 1281386064
1164266611 https://github.com/pydata/xarray/issues/6716#issuecomment-1164266611 https://api.github.com/repos/pydata/xarray/issues/6716 IC_kwDOAMm_X85FZUxz spencerkclark 6628425 2022-06-23T10:57:10Z 2022-06-23T10:57:10Z MEMBER

6717 should fix the time decoding errors.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ⚠️ Nightly upstream-dev CI failed ⚠️ 1281386064
1164256154 https://github.com/pydata/xarray/issues/6716#issuecomment-1164256154 https://api.github.com/repos/pydata/xarray/issues/6716 IC_kwDOAMm_X85FZSOa keewis 14808389 2022-06-23T10:44:59Z 2022-06-23T10:45:29Z MEMBER

@dcherian, do you have an idea about where the IntervalIndex failures could come from? pandas-dev/pandas#47365, maybe?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ⚠️ Nightly upstream-dev CI failed ⚠️ 1281386064
1163812213 https://github.com/pydata/xarray/issues/6716#issuecomment-1163812213 https://api.github.com/repos/pydata/xarray/issues/6716 IC_kwDOAMm_X85FXl11 spencerkclark 6628425 2022-06-23T01:02:35Z 2022-06-23T01:02:35Z MEMBER

I will investigate these cftime failures more in a bit, but I suspect they may be related to these recent PRs in pandas. It appears they are working towards adding support for non-nanosecond-precision datetimes, which is quite an interesting development.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ⚠️ Nightly upstream-dev CI failed ⚠️ 1281386064

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