issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 539988974 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • dcherian · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
621309942 https://github.com/pydata/xarray/pull/3643#issuecomment-621309942 https://api.github.com/repos/pydata/xarray/issues/3643 MDEyOklzc3VlQ29tbWVudDYyMTMwOTk0Mg== dcherian 2448579 2020-04-29T16:08:03Z 2020-04-29T16:08:03Z MEMBER

IMO @keewis you should merge this if you think its ready.

even if it's just to clarify why we accept different types in those functions: I think init may convert its arguments so it supports more types than array_ufunc (I don't know about the others, though).

open an issue for this?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Pint support for DataArray 539988974
609812461 https://github.com/pydata/xarray/pull/3643#issuecomment-609812461 https://api.github.com/repos/pydata/xarray/issues/3643 MDEyOklzc3VlQ29tbWVudDYwOTgxMjQ2MQ== dcherian 2448579 2020-04-06T13:59:07Z 2020-04-06T13:59:07Z MEMBER

pint tries to add xarray to its known non-handled types

I don't know much about this stuff can't pint have just a list of handled types and return NotImplementedfor anything else?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Pint support for DataArray 539988974
605675581 https://github.com/pydata/xarray/pull/3643#issuecomment-605675581 https://api.github.com/repos/pydata/xarray/issues/3643 MDEyOklzc3VlQ29tbWVudDYwNTY3NTU4MQ== dcherian 2448579 2020-03-29T18:00:54Z 2020-03-29T18:00:54Z MEMBER

, but some of these seem to depend on DataArray.array_function which is not defined

Let's open an issue for visibility.

we have a few issues with non-numpy libraries (scipy, bottleneck, numbagg) and the semi-public numpy.lib.stride_tricks.as_strided and of course the indexing does not work either.

This seems OK for now.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Pint support for DataArray 539988974

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