issue_comments

Table actions

4 rows where issue = 403458737 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
472137075 https://github.com/pydata/xarray/pull/2715#issuecomment-472137075 https://api.github.com/repos/pydata/xarray/issues/2715 MDEyOklzc3VlQ29tbWVudDQ3MjEzNzA3NQ== shoyer 1217238 2019-03-12T18:57:44Z 2019-03-12T18:57:44Z MEMBER

Hopefully quite soon! see https://github.com/pydata/xarray/pull/2777 for current status

On Tue, Mar 12, 2019 at 10:31 AM David Hoese notifications@github.com wrote:

@shoyer https://github.com/shoyer Any idea when a 0.11.4 or 0.12 will be released? I'm trying to work around some other rasterio bugs and would like to remove the restriction on the rasterio version used in my CI tests, but that requires this PR.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/pull/2715#issuecomment-472102830, or mute the thread https://github.com/notifications/unsubscribe-auth/ABKS1hs0lknMUSnOP9A_Qw0124V8HZllks5vV-SGgaJpZM4aUQen . 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix CRS being WKT instead of PROJ.4 403458737
461099466 https://github.com/pydata/xarray/pull/2715#issuecomment-461099466 https://api.github.com/repos/pydata/xarray/issues/2715 MDEyOklzc3VlQ29tbWVudDQ2MTA5OTQ2Ng== shoyer 1217238 2019-02-06T16:56:17Z 2019-02-06T16:56:17Z MEMBER

thanks David, that looks great

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix CRS being WKT instead of PROJ.4 403458737
461094509 https://github.com/pydata/xarray/pull/2715#issuecomment-461094509 https://api.github.com/repos/pydata/xarray/issues/2715 MDEyOklzc3VlQ29tbWVudDQ2MTA5NDUwOQ== shoyer 1217238 2019-02-06T16:43:39Z 2019-02-06T16:43:39Z MEMBER

This PR isn't changing any functionality. It is making the same functionality available with newer versions of rasterio.

OK, good point. I do still try to lean towards adding notes about bug fixes in "what's new" but it isn't strictly required.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix CRS being WKT instead of PROJ.4 403458737
461080045 https://github.com/pydata/xarray/pull/2715#issuecomment-461080045 https://api.github.com/repos/pydata/xarray/issues/2715 MDEyOklzc3VlQ29tbWVudDQ2MTA4MDA0NQ== shoyer 1217238 2019-02-06T16:06:58Z 2019-02-06T16:06:58Z MEMBER

Does this need a whats-new entry?

Yes, I would recommend that here -- especially for cases where we're changing behavior without a deprecation cycle (which is sometime the best path forward)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix CRS being WKT instead of PROJ.4 403458737

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