issue_comments

Table actions

2 rows where issue = 227858207 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 · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
482225459 https://github.com/pydata/xarray/issues/1403#issuecomment-482225459 https://api.github.com/repos/pydata/xarray/issues/1403 MDEyOklzc3VlQ29tbWVudDQ4MjIyNTQ1OQ== shoyer 1217238 2019-04-11T17:53:15Z 2019-04-11T17:53:15Z MEMBER

Closing this in favor of the bigger discussion in https://github.com/pydata/xarray/issues/2217

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Lost coords after multiplication 227858207
300834776 https://github.com/pydata/xarray/issues/1403#issuecomment-300834776 https://api.github.com/repos/pydata/xarray/issues/1403 MDEyOklzc3VlQ29tbWVudDMwMDgzNDc3Ng== shoyer 1217238 2017-05-11T15:56:32Z 2017-05-11T15:56:32Z MEMBER

The problem here is that your coordinates differ slightly on each file: In [14]: abs(advt.TLAT - tarea.TLAT).max() Out[14]: <xarray.DataArray 'TLAT' ()> array(4.547473508864641e-13)

This does come up with some frequency, but unfortunately, it's hard to know a priori whether differences in floating point values are meaningful or just due to loss of numerical precision.

One way to fix this would be to add a tolerance keyword argument of some sort to xarray.Variable.equals(), which we could allow setting via xarray.set_options() for arithmetic. Then you could write something like: with xarray.set_options(float_tolerance=1e-8): result = advt * tarea and still preserve coordinates.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Lost coords after multiplication 227858207

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