issue_comments

Table actions

5 rows where issue = 620009114 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 2

issue 1

  • [BUG] xr.concat inverts coordinates order · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
695191581 https://github.com/pydata/xarray/issues/4072#issuecomment-695191581 https://api.github.com/repos/pydata/xarray/issues/4072 MDEyOklzc3VlQ29tbWVudDY5NTE5MTU4MQ== keewis 14808389 2020-09-19T09:41:00Z 2020-09-19T09:41:00Z MEMBER

closed by #4419

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [BUG] xr.concat inverts coordinates order 620009114
695085588 https://github.com/pydata/xarray/issues/4072#issuecomment-695085588 https://api.github.com/repos/pydata/xarray/issues/4072 MDEyOklzc3VlQ29tbWVudDY5NTA4NTU4OA== keewis 14808389 2020-09-18T21:04:27Z 2020-09-18T21:04:54Z MEMBER

sorry, I forgot to remove the "closes" item in #4409. This will be fixed by #4419.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [BUG] xr.concat inverts coordinates order 620009114
630124227 https://github.com/pydata/xarray/issues/4072#issuecomment-630124227 https://api.github.com/repos/pydata/xarray/issues/4072 MDEyOklzc3VlQ29tbWVudDYzMDEyNDIyNw== clausmichele 31700619 2020-05-18T11:38:10Z 2020-05-18T11:38:10Z CONTRIBUTOR

@keewis yes you are right, but still a consistent ordering would be less confusing, including maybe also the Dimensions field. Now Dimensions shows first x and then y, even though the data itself has y,x ordering.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [BUG] xr.concat inverts coordinates order 620009114
630118916 https://github.com/pydata/xarray/issues/4072#issuecomment-630118916 https://api.github.com/repos/pydata/xarray/issues/4072 MDEyOklzc3VlQ29tbWVudDYzMDExODkxNg== kmuehlbauer 5821660 2020-05-18T11:26:13Z 2020-05-18T11:26:13Z MEMBER

This rings a bell! It has be discussed in https://github.com/pydata/xarray/issues/2811. I've done extensive checks back then, but didn't come up with an PR.

My workaround or solution is outlined in this comment. Code might have been changed!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [BUG] xr.concat inverts coordinates order 620009114
630114341 https://github.com/pydata/xarray/issues/4072#issuecomment-630114341 https://api.github.com/repos/pydata/xarray/issues/4072 MDEyOklzc3VlQ29tbWVudDYzMDExNDM0MQ== keewis 14808389 2020-05-18T11:16:02Z 2020-05-18T11:16:02Z MEMBER

don't use the Coordinates section to check the order. Dataset objects may have multiple data variables (each with a possibly different order of dimensions) so for displaying it needs to define some kind of order.

What you want to compare is the order of dimensions referenced by a variable: <xarray.Dataset> Dimensions: (time: 1, x: 10, y: 10) Coordinates: * time (time) int64 0 * y (y) int64 0 1 2 3 4 5 6 7 8 9 * x (x) int64 0 1 2 3 4 5 6 7 8 9 Data variables: data (time, y, x) bool False False False False ... False False False ^^^^^^^^^^^^ and you will notice that the order does not change.

To make this less confusing, maybe we should always sort the coordinates when displaying them? I'm guessing that right now they are displayed in the order they were added to the coordinates.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [BUG] xr.concat inverts coordinates order 620009114

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