issue_comments
4 rows where issue = 125708367 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- DataArrays should display their coordinates in the natural order · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 211418692 | https://github.com/pydata/xarray/issues/712#issuecomment-211418692 | https://api.github.com/repos/pydata/xarray/issues/712 | MDEyOklzc3VlQ29tbWVudDIxMTQxODY5Mg== | shoyer 1217238 | 2016-04-18T15:04:30Z | 2016-04-18T15:04:30Z | MEMBER | OK, I didn't read your first post carefully last time. Your complaint was about the order of coordinates in We could add some sort of ad-hoc adjustment to the order in which we display coordinates, but I'm reluctant because it's not obvious to me what that "correct" order would be. For example, that you can directly supply the I suppose once principled choice would always be to display coordinates corresponding to dimensions first in lists of coordinates, and to always display them in the same order as dimensions. If we do this, it should be consistent between both DataArray and Dataset. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
DataArrays should display their coordinates in the natural order 125708367 | |
| 174843391 | https://github.com/pydata/xarray/issues/712#issuecomment-174843391 | https://api.github.com/repos/pydata/xarray/issues/712 | MDEyOklzc3VlQ29tbWVudDE3NDg0MzM5MQ== | shoyer 1217238 | 2016-01-26T05:41:28Z | 2016-01-26T05:41:28Z | MEMBER | This should be fixed in v0.7.0... please reopen if it resurfaces. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
DataArrays should display their coordinates in the natural order 125708367 | |
| 170155759 | https://github.com/pydata/xarray/issues/712#issuecomment-170155759 | https://api.github.com/repos/pydata/xarray/issues/712 | MDEyOklzc3VlQ29tbWVudDE3MDE1NTc1OQ== | shoyer 1217238 | 2016-01-08T23:28:44Z | 2016-01-08T23:28:44Z | MEMBER | yes, in the next week, hopefully. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
DataArrays should display their coordinates in the natural order 125708367 | |
| 170149315 | https://github.com/pydata/xarray/issues/712#issuecomment-170149315 | https://api.github.com/repos/pydata/xarray/issues/712 | MDEyOklzc3VlQ29tbWVudDE3MDE0OTMxNQ== | shoyer 1217238 | 2016-01-08T22:49:37Z | 2016-01-08T22:50:03Z | MEMBER | I think this may have been fixed by the recent rewrite of DataArray internals. On master, I have: ``` In [2]: d1 Out[2]: <xray.DataArray (foo: 2, bar: 2)> array([[ 0.00000000e+000, 0.00000000e+000], [ 2.15725662e-314, 2.15893204e-314]]) Coordinates: * foo (foo) int64 0 1 * bar (bar) int64 0 1 In [3]: d2 Out[3]: <xray.DataArray (bar: 2, foo: 2)> array([[ 0.00000000e+000, 0.00000000e+000], [ 2.15906985e-314, 2.14458868e-314]]) Coordinates: * bar (bar) int64 0 1 * foo (foo) int64 0 1 ``` |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
DataArrays should display their coordinates in the natural order 125708367 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1